Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91532b5298d7c1cd36a940470c2c1990d6b97f2ebfdcc06d69af7bb719edea0b

Tx prefix hash: 46118b1e1de89c9b48f760ae411645374bdccc6b9d125742c9dceb7b044726ba
Tx public key: 3c2037545169957043ba37fad8ac78ff38ea200c76c14bb96e6ad3b43ebb6cd3
Timestamp: 1713270423 Timestamp [UCT]: 2024-04-16 12:27:03 Age [y:d:h:m:s]: 00:357:04:00:56
Block: 1001743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255361 RingCT/type: yes/0
Extra: 013c2037545169957043ba37fad8ac78ff38ea200c76c14bb96e6ad3b43ebb6cd30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b8b29fb6e9d34ea521fa8d5dc1c88efa41391676a1af3b4fff30bdef6d1a784 0.600000000000 1462255 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": 1001753, "vin": [ { "gen": { "height": 1001743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b8b29fb6e9d34ea521fa8d5dc1c88efa41391676a1af3b4fff30bdef6d1a784" } } ], "extra": [ 1, 60, 32, 55, 84, 81, 105, 149, 112, 67, 186, 55, 250, 216, 172, 120, 255, 56, 234, 32, 12, 118, 193, 75, 185, 110, 106, 211, 180, 62, 187, 108, 211, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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