Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcb29a37c3c46e784bf45bd4e0b3fdc6c32f4f7a9eee8540781e5caff0b3fde3

Tx prefix hash: a95e36ff38f967c011ef3039ec8242ec39d929a4ed58be6c173bee478c92f57c
Tx public key: 21ddb729e57e705ec1e30b21af316db2568f4fb4cbb2414fddd81b3381fe0304
Timestamp: 1713292220 Timestamp [UCT]: 2024-04-16 18:30:20 Age [y:d:h:m:s]: 01:204:04:00:00
Block: 1001927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404579 RingCT/type: yes/0
Extra: 0121ddb729e57e705ec1e30b21af316db2568f4fb4cbb2414fddd81b3381fe030402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ccf75438d781bee56edbbcfef16054d8a888f595ee9336e943a9613648dc7d9 0.600000000000 1462441 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": 1001937, "vin": [ { "gen": { "height": 1001927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ccf75438d781bee56edbbcfef16054d8a888f595ee9336e943a9613648dc7d9" } } ], "extra": [ 1, 33, 221, 183, 41, 229, 126, 112, 94, 193, 227, 11, 33, 175, 49, 109, 178, 86, 143, 79, 180, 203, 178, 65, 79, 221, 216, 27, 51, 129, 254, 3, 4, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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