Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c6c6fdd7ce54a7dc58c384ada0fce778cd2d6e89a655817a52be864476f19c

Tx prefix hash: be677db94358ee2bb8a7bcea1ff2cd01dd0e090891c6c23da595a80d30c07080
Tx public key: 558ff781a8815701c76c275074bbd4c2db4e5a1d43ce3d98c379e904b28be41e
Timestamp: 1715892591 Timestamp [UCT]: 2024-05-16 20:49:51 Age [y:d:h:m:s]: 00:305:09:42:28
Block: 1023507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218286 RingCT/type: yes/0
Extra: 01558ff781a8815701c76c275074bbd4c2db4e5a1d43ce3d98c379e904b28be41e02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afd6c96aae473ff96c552cdc6d57e0118a1dca74872f98d205223f0b7294f413 0.600000000000 1488530 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": 1023517, "vin": [ { "gen": { "height": 1023507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afd6c96aae473ff96c552cdc6d57e0118a1dca74872f98d205223f0b7294f413" } } ], "extra": [ 1, 85, 143, 247, 129, 168, 129, 87, 1, 199, 108, 39, 80, 116, 187, 212, 194, 219, 78, 90, 29, 67, 206, 61, 152, 195, 121, 233, 4, 178, 139, 228, 30, 2, 17, 0, 0, 0, 3, 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