Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74b736b2854ca5e5331ddf200148b5f22934a0e2fd5d53504089ecb772e6ea44

Tx prefix hash: 9752943a264179d7708be3f7626c8bf0295e474bd80f3abb34bfd43c8dea8416
Tx public key: 6cb360df148bc855e2c6f3c692445585647bcd6c4eab59a93bdf5b4ebf3a61fe
Timestamp: 1714136424 Timestamp [UCT]: 2024-04-26 13:00:24 Age [y:d:h:m:s]: 00:202:21:22:33
Block: 1008944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145239 RingCT/type: yes/0
Extra: 016cb360df148bc855e2c6f3c692445585647bcd6c4eab59a93bdf5b4ebf3a61fe0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c8152c9fe909f1a003d54a3733879def6830d921f039539537f3c7ad2e820d4 0.600000000000 1470464 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": 1008954, "vin": [ { "gen": { "height": 1008944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c8152c9fe909f1a003d54a3733879def6830d921f039539537f3c7ad2e820d4" } } ], "extra": [ 1, 108, 179, 96, 223, 20, 139, 200, 85, 226, 198, 243, 198, 146, 68, 85, 133, 100, 123, 205, 108, 78, 171, 89, 169, 59, 223, 91, 78, 191, 58, 97, 254, 2, 17, 0, 0, 0, 2, 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