Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58c86a85bf98f86c026b2ca3cf4f6b8ebd2731861251e98a357fa37792cecb82

Tx prefix hash: 50a5fdd51b95ec0cde41e961913601cdf088059a063d22c86e044f3dea670315
Tx public key: 60cfb062f3cbca136dc4fcc60ef8974f03158ce3ffd69c3760cb3d1c508a3131
Timestamp: 1714266753 Timestamp [UCT]: 2024-04-28 01:12:33 Age [y:d:h:m:s]: 01:194:13:39:44
Block: 1010019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397701 RingCT/type: yes/0
Extra: 0160cfb062f3cbca136dc4fcc60ef8974f03158ce3ffd69c3760cb3d1c508a31310211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83c0faf26b0b60a866ccafafb740576a318b9c989e9011ae20b48b084d0e869a 0.600000000000 1471853 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": 1010029, "vin": [ { "gen": { "height": 1010019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83c0faf26b0b60a866ccafafb740576a318b9c989e9011ae20b48b084d0e869a" } } ], "extra": [ 1, 96, 207, 176, 98, 243, 203, 202, 19, 109, 196, 252, 198, 14, 248, 151, 79, 3, 21, 140, 227, 255, 214, 156, 55, 96, 203, 61, 28, 80, 138, 49, 49, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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