Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83a99029fea72228ad2cdb662ddf0f1fd9dbf16d28922cdbabf4f202ced0b6fd

Tx prefix hash: fc616ffdb26d7511fad9647acb0983e30e76b7d211c0db0db3f01f95f4dc2529
Tx public key: fc6ea3abab96075da94b8f77b7cffce2e206de68d90a6e3575221030e12f9323
Timestamp: 1746371530 Timestamp [UCT]: 2025-05-04 15:12:10 Age [y:d:h:m:s]: 00:200:23:51:16
Block: 1275663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141357 RingCT/type: yes/0
Extra: 01fc6ea3abab96075da94b8f77b7cffce2e206de68d90a6e3575221030e12f932302110000000b1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 874b9ee9d2470104a4cac76a875dddf1a535c332c42ae1e7ae3ff7ab636dddf7 0.600000000000 1762978 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": 1275673, "vin": [ { "gen": { "height": 1275663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "874b9ee9d2470104a4cac76a875dddf1a535c332c42ae1e7ae3ff7ab636dddf7" } } ], "extra": [ 1, 252, 110, 163, 171, 171, 150, 7, 93, 169, 75, 143, 119, 183, 207, 252, 226, 226, 6, 222, 104, 217, 10, 110, 53, 117, 34, 16, 48, 225, 47, 147, 35, 2, 17, 0, 0, 0, 11, 31, 144, 81, 122, 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