Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a589ca79a20e41556576b032f4ab8e939df7d292378f2e48a96793ccb6f81862

Tx prefix hash: be22068d92726c5dffcd81785dd22b4f9f8d4351628bd3503d59f823c06b5bb2
Tx public key: 0a5db9d431e6a8e8f5da8153963aeebed718cf211dcea2b852984117cbfc1bbc
Timestamp: 1738601481 Timestamp [UCT]: 2025-02-03 16:51:21 Age [y:d:h:m:s]: 00:290:23:17:41
Block: 1211329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205722 RingCT/type: yes/0
Extra: 010a5db9d431e6a8e8f5da8153963aeebed718cf211dcea2b852984117cbfc1bbc0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bad9b973cbc1438c0011e47c9a4f9aef8abc0c04218f68a20cbd01d748c0980 0.600000000000 1698090 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1211339, "vin": [ { "gen": { "height": 1211329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bad9b973cbc1438c0011e47c9a4f9aef8abc0c04218f68a20cbd01d748c0980" } } ], "extra": [ 1, 10, 93, 185, 212, 49, 230, 168, 232, 245, 218, 129, 83, 150, 58, 238, 190, 215, 24, 207, 33, 29, 206, 162, 184, 82, 152, 65, 23, 203, 252, 27, 188, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8