Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6f8eb312e0c9f01c905d003fc12f54525d883452368aaa617671e5b2328dd62

Tx prefix hash: 8181a8afdd59b4504121f8f7e46a9358c7bde9044baf99dc73a76ca11b037f2d
Tx public key: 333cdcba4d2f20f975296b8aa607a7dc3e43d563b91d25f74ff01d34662b32ea
Timestamp: 1705371138 Timestamp [UCT]: 2024-01-16 02:12:18 Age [y:d:h:m:s]: 01:300:18:33:32
Block: 936245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473798 RingCT/type: yes/0
Extra: 01333cdcba4d2f20f975296b8aa607a7dc3e43d563b91d25f74ff01d34662b32ea02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef7cb4b1d56b28861e2a2f4379c34fd3e55df3623afc62c8d70e529d583a3fcc 0.600000000000 1394269 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": 936255, "vin": [ { "gen": { "height": 936245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef7cb4b1d56b28861e2a2f4379c34fd3e55df3623afc62c8d70e529d583a3fcc" } } ], "extra": [ 1, 51, 60, 220, 186, 77, 47, 32, 249, 117, 41, 107, 138, 166, 7, 167, 220, 62, 67, 213, 99, 185, 29, 37, 247, 79, 240, 29, 52, 102, 43, 50, 234, 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