Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd01a008f6d3565594a0bf4fae89b10df6ada89a024b8f22702b8d51e1accd4b

Tx prefix hash: 09196a99958363c8e1275044c19813d05d7ea8ffaa37aa5793a910ece036eb58
Tx public key: 1cd18f20c41821e55ed97b9ef4d59dc6e4e55876b68280daa0ccacaf0a537940
Timestamp: 1724652886 Timestamp [UCT]: 2024-08-26 06:14:46 Age [y:d:h:m:s]: 00:222:09:52:18
Block: 1096115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158836 RingCT/type: yes/0
Extra: 011cd18f20c41821e55ed97b9ef4d59dc6e4e55876b68280daa0ccacaf0a537940021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2c2e4b8efc78a18dd26880387961ef78609f2f320b7a5da7ab45ad5c48d0d38 0.600000000000 1571302 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": 1096125, "vin": [ { "gen": { "height": 1096115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2c2e4b8efc78a18dd26880387961ef78609f2f320b7a5da7ab45ad5c48d0d38" } } ], "extra": [ 1, 28, 209, 143, 32, 196, 24, 33, 229, 94, 217, 123, 158, 244, 213, 157, 198, 228, 229, 88, 118, 182, 130, 128, 218, 160, 204, 172, 175, 10, 83, 121, 64, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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