Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9d7e1f707817db7eb58ab54154f8c905eb1c757350c7465a87c16a055436159

Tx prefix hash: 558f298f542283c6be7945985e131d36f89a8ad60fee4835ef24a6a2d39f3c6a
Tx public key: e8df00b7043b0dd20aa2d1de4b8f79e5c85d4a9442054ce8f88d2dc82924aa23
Timestamp: 1694571667 Timestamp [UCT]: 2023-09-13 02:21:07 Age [y:d:h:m:s]: 01:244:23:12:30
Block: 846919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436209 RingCT/type: yes/0
Extra: 01e8df00b7043b0dd20aa2d1de4b8f79e5c85d4a9442054ce8f88d2dc82924aa23021100000006faf35c9c000000000000000000

1 output(s) for total of 0.958971811000 dcy

stealth address amount amount idx
00: 19ec63213d041419d86e38892d016fa69de2985e4d16a11a9f683b6e464f37eb 0.958971811000 1300411 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": 846929, "vin": [ { "gen": { "height": 846919 } } ], "vout": [ { "amount": 958971811, "target": { "key": "19ec63213d041419d86e38892d016fa69de2985e4d16a11a9f683b6e464f37eb" } } ], "extra": [ 1, 232, 223, 0, 183, 4, 59, 13, 210, 10, 162, 209, 222, 75, 143, 121, 229, 200, 93, 74, 148, 66, 5, 76, 232, 248, 141, 45, 200, 41, 36, 170, 35, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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