Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e675b4c189813157724625caf51adef17ce4586d130a2af2ea0da4619a700ac

Tx prefix hash: 69b37d7164dd2c357caa83c6852113a634cea18962fa979b8ddabe473d31ac7b
Tx public key: 1f3bec117d831ee33e9574df563c6e957a6b6f664df8976006b56a0201f04594
Timestamp: 1583231516 Timestamp [UCT]: 2020-03-03 10:31:56 Age [y:d:h:m:s]: 04:342:11:43:34
Block: 75212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139152 RingCT/type: yes/0
Extra: 011f3bec117d831ee33e9574df563c6e957a6b6f664df8976006b56a0201f0459402110000003bc71d3ff9000000000000000000

1 output(s) for total of 345.773908428000 dcy

stealth address amount amount idx
00: 29b7f628a1ff39d9ceefc403c786409ce76b115f580e9eb6e3a63b79918cbbc2 345.773908428000 139117 of 0

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": 75222, "vin": [ { "gen": { "height": 75212 } } ], "vout": [ { "amount": 345773908428, "target": { "key": "29b7f628a1ff39d9ceefc403c786409ce76b115f580e9eb6e3a63b79918cbbc2" } } ], "extra": [ 1, 31, 59, 236, 17, 125, 131, 30, 227, 62, 149, 116, 223, 86, 60, 110, 149, 122, 107, 111, 102, 77, 248, 151, 96, 6, 181, 106, 2, 1, 240, 69, 148, 2, 17, 0, 0, 0, 59, 199, 29, 63, 249, 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