Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 164669c74ccccca77e51130818e114b4d9a95b099ce74f30213c58c79985d0be

Tx prefix hash: 667136cb880b7819f83c7969566387b7f6f823cdc2589fc3c59e80547b63d389
Tx public key: a463e3d323c9e2a00ed3f7c41dfc070c7d9a2aa6c6998519c5bff2fef2c1bb78
Timestamp: 1762051672 Timestamp [UCT]: 2025-11-02 02:47:52 Age [y:d:h:m:s]: 00:007:13:46:05
Block: 1403064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5428 RingCT/type: yes/0
Extra: 01a463e3d323c9e2a00ed3f7c41dfc070c7d9a2aa6c6998519c5bff2fef2c1bb7802110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c940679a985e67a43a6afc54a3587aae3244bab6e250c39bdc39371865faca1 0.600000000000 1891391 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": 1403074, "vin": [ { "gen": { "height": 1403064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c940679a985e67a43a6afc54a3587aae3244bab6e250c39bdc39371865faca1" } } ], "extra": [ 1, 164, 99, 227, 211, 35, 201, 226, 160, 14, 211, 247, 196, 29, 252, 7, 12, 125, 154, 42, 166, 198, 153, 133, 25, 197, 191, 242, 254, 242, 193, 187, 120, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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