Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1a85f2ecc0047dd4ab5bbfa1f9e9aeb09d36117641b90abdcf548e3258d949

Tx prefix hash: 540e83ed8408c4c8e1d3794c6b91a7397d575e4e9e2bd1a57e49ca7232d39d38
Tx public key: 7df3dd4fbe11a3d2ebe562e0245f15063977ff5648d19a60726dd0688811b7f0
Timestamp: 1717167105 Timestamp [UCT]: 2024-05-31 14:51:45 Age [y:d:h:m:s]: 00:180:23:45:02
Block: 1034080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129540 RingCT/type: yes/0
Extra: 017df3dd4fbe11a3d2ebe562e0245f15063977ff5648d19a60726dd0688811b7f002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b74d4cff017c6e5f5df5d283e071c400bf547539568d3d19a9f0d214fe493db 0.600000000000 1502553 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": 1034090, "vin": [ { "gen": { "height": 1034080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b74d4cff017c6e5f5df5d283e071c400bf547539568d3d19a9f0d214fe493db" } } ], "extra": [ 1, 125, 243, 221, 79, 190, 17, 163, 210, 235, 229, 98, 224, 36, 95, 21, 6, 57, 119, 255, 86, 72, 209, 154, 96, 114, 109, 208, 104, 136, 17, 183, 240, 2, 17, 0, 0, 0, 1, 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