Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ec8a2f4c6bf76cc700ec27822c58bfa15d77cc1d5f5af700c42179d41eff00

Tx prefix hash: ea75723980d99f78777c9cf99038eb913e170f4a3b8ccb3d3a24279f78b6af9e
Tx public key: f9751a3118e5871c40a38c3f4904ebbaaf30062aa5809505b9e106fb0d4a920f
Timestamp: 1734944898 Timestamp [UCT]: 2024-12-23 09:08:18 Age [y:d:h:m:s]: 00:174:19:20:07
Block: 1181368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124638 RingCT/type: yes/0
Extra: 01f9751a3118e5871c40a38c3f4904ebbaaf30062aa5809505b9e106fb0d4a920f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6e7d9a47cf8a64691c3e823007c3444a93f16ae89d4515c07ce13700c624488 0.600000000000 1667787 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": 1181378, "vin": [ { "gen": { "height": 1181368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6e7d9a47cf8a64691c3e823007c3444a93f16ae89d4515c07ce13700c624488" } } ], "extra": [ 1, 249, 117, 26, 49, 24, 229, 135, 28, 64, 163, 140, 63, 73, 4, 235, 186, 175, 48, 6, 42, 165, 128, 149, 5, 185, 225, 6, 251, 13, 74, 146, 15, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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