Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 814b02f542f9a811eb6eaaec2bd660755fabe5364728d5420cf78b207266587d

Tx prefix hash: f28af7a1055dff8a76883e648f45b6007111c4a71f46d29892b7b76738f30ad0
Tx public key: 739f3d082a7c2e7d3fe24e53338ab767c41b674d77a47615caa1cc47e2f4d0eb
Timestamp: 1714200864 Timestamp [UCT]: 2024-04-27 06:54:24 Age [y:d:h:m:s]: 00:302:06:14:20
Block: 1009470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216041 RingCT/type: yes/0
Extra: 01739f3d082a7c2e7d3fe24e53338ab767c41b674d77a47615caa1cc47e2f4d0eb0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09e446fbf54ac59c87286fef0064fdc3b7a2a23da4174db0c6775e5ffcd07f95 0.600000000000 1471152 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": 1009480, "vin": [ { "gen": { "height": 1009470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09e446fbf54ac59c87286fef0064fdc3b7a2a23da4174db0c6775e5ffcd07f95" } } ], "extra": [ 1, 115, 159, 61, 8, 42, 124, 46, 125, 63, 226, 78, 83, 51, 138, 183, 103, 196, 27, 103, 77, 119, 164, 118, 21, 202, 161, 204, 71, 226, 244, 208, 235, 2, 17, 0, 0, 0, 3, 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