Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8687a908729e409242fe09c542ede4459df8c0ee0b58fb0f80769243d71fff8c

Tx prefix hash: b42146027a14a1dd841e1a758e47c5f7fe02d1d532d6b32e4c412c0cb4d63a60
Tx public key: 8c0e5ada21977cf24341ba2feba33e175a345ff7996c931d07b99ef9a298a667
Timestamp: 1722112535 Timestamp [UCT]: 2024-07-27 20:35:35 Age [y:d:h:m:s]: 00:260:23:57:54
Block: 1075070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186453 RingCT/type: yes/0
Extra: 018c0e5ada21977cf24341ba2feba33e175a345ff7996c931d07b99ef9a298a66702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73a7ac56b5254d5d75626dfe2eb0ea38b681369f4a65df5dd19b7d5ca65b81a4 0.600000000000 1547593 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": 1075080, "vin": [ { "gen": { "height": 1075070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73a7ac56b5254d5d75626dfe2eb0ea38b681369f4a65df5dd19b7d5ca65b81a4" } } ], "extra": [ 1, 140, 14, 90, 218, 33, 151, 124, 242, 67, 65, 186, 47, 235, 163, 62, 23, 90, 52, 95, 247, 153, 108, 147, 29, 7, 185, 158, 249, 162, 152, 166, 103, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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