Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 623f2dd71d02fc8bf77af53f88a18cc15ad62cd334adcf72d8f318f9b266aa88

Tx prefix hash: da3ba685930b55cdcf08149b2bed95ce31bc94ef868b651d7df44212b38b0157
Tx public key: 00973793b78aa9efd508395773acf28a1e711ee5d25343e7d63e804ef19b0c74
Timestamp: 1669489883 Timestamp [UCT]: 2022-11-26 19:11:23 Age [y:d:h:m:s]: 02:141:11:22:29
Block: 639701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 622829 RingCT/type: yes/0
Extra: 0100973793b78aa9efd508395773acf28a1e711ee5d25343e7d63e804ef19b0c7402110000000a74b6d784000000000000000000

1 output(s) for total of 4.660205157000 dcy

stealth address amount amount idx
00: 07723b6cbf1b93670d987ef8231f1548e04ad1e78c8f1a60d600f518dc74c56e 4.660205157000 1079372 of 0

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": 639711, "vin": [ { "gen": { "height": 639701 } } ], "vout": [ { "amount": 4660205157, "target": { "key": "07723b6cbf1b93670d987ef8231f1548e04ad1e78c8f1a60d600f518dc74c56e" } } ], "extra": [ 1, 0, 151, 55, 147, 183, 138, 169, 239, 213, 8, 57, 87, 115, 172, 242, 138, 30, 113, 30, 229, 210, 83, 67, 231, 214, 62, 128, 78, 241, 155, 12, 116, 2, 17, 0, 0, 0, 10, 116, 182, 215, 132, 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