Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1cbc1b8e341a1b802e37958d669eddc9a90bf3241a7c80580736ea3c76d5494

Tx prefix hash: 3bc4cc191c5f9ccd501138b6377358dba16aba1076d54640d785ef4cc6fa061d
Tx public key: 18080e917f6e80eb2cd2d4afb0222c77ee5ef2b1c260323c01970a7d37d37b0e
Timestamp: 1735174407 Timestamp [UCT]: 2024-12-26 00:53:27 Age [y:d:h:m:s]: 00:095:08:11:06
Block: 1183238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67924 RingCT/type: yes/0
Extra: 0118080e917f6e80eb2cd2d4afb0222c77ee5ef2b1c260323c01970a7d37d37b0e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d397951b07e3fd94d2f529096e71fe61faa1573dceed8693d62941b638d02eaf 0.600000000000 1669679 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": 1183248, "vin": [ { "gen": { "height": 1183238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d397951b07e3fd94d2f529096e71fe61faa1573dceed8693d62941b638d02eaf" } } ], "extra": [ 1, 24, 8, 14, 145, 127, 110, 128, 235, 44, 210, 212, 175, 176, 34, 44, 119, 238, 94, 242, 177, 194, 96, 50, 60, 1, 151, 10, 125, 55, 211, 123, 14, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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