Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f209cae521ccdb90d1d70945d74916fa25e721cfd25e0a643abcf9f2f2dc040

Tx prefix hash: ff3c47342651b1be9323c18f18af88908bf6cce0500162510d9d8e91fdea2d9c
Tx public key: 6c1fe4794bba6c2cab9eee80afadb8cfacd67c32fa63b1ee07f4a58cd5d0c706
Timestamp: 1706676136 Timestamp [UCT]: 2024-01-31 04:42:16 Age [y:d:h:m:s]: 01:126:13:01:49
Block: 947070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351581 RingCT/type: yes/0
Extra: 016c1fe4794bba6c2cab9eee80afadb8cfacd67c32fa63b1ee07f4a58cd5d0c7060211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b02cbbe435d348a251c67ea997bd7d4e0d78fc00d879681d8848ac3786e9d7 0.600000000000 1405418 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": 947080, "vin": [ { "gen": { "height": 947070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b02cbbe435d348a251c67ea997bd7d4e0d78fc00d879681d8848ac3786e9d7" } } ], "extra": [ 1, 108, 31, 228, 121, 75, 186, 108, 44, 171, 158, 238, 128, 175, 173, 184, 207, 172, 214, 124, 50, 250, 99, 177, 238, 7, 244, 165, 140, 213, 208, 199, 6, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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