Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0b93e1ef7f2c18a17f80092f5d6f90d9593dfedf2f429d2ee30eaa39c46dcc6

Tx prefix hash: 2c4b399f3fdf7c9b9f9d568e89037e8bfaa5a761f5482053b0b8a15b434da7f6
Tx public key: a5d147ff8c44b760369ad1f10ad76dd12acf8627bfa2b56ed917b47fdf2ac2af
Timestamp: 1712717765 Timestamp [UCT]: 2024-04-10 02:56:05 Age [y:d:h:m:s]: 01:291:19:58:06
Block: 997160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467180 RingCT/type: yes/0
Extra: 01a5d147ff8c44b760369ad1f10ad76dd12acf8627bfa2b56ed917b47fdf2ac2af02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f69b6a659294cc44e5b5212a8e8f683387ce4276bf049f19a939dd1b209a284 0.600000000000 1457590 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": 997170, "vin": [ { "gen": { "height": 997160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f69b6a659294cc44e5b5212a8e8f683387ce4276bf049f19a939dd1b209a284" } } ], "extra": [ 1, 165, 209, 71, 255, 140, 68, 183, 96, 54, 154, 209, 241, 10, 215, 109, 209, 42, 207, 134, 39, 191, 162, 181, 110, 217, 23, 180, 127, 223, 42, 194, 175, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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