Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98f1e8742d881a958494b1ddac2b934b0f45867104270ee3919195b0585b75d8

Tx prefix hash: 0c0543f987ab94de678f1cfdb3ba0efbb7ba2ec900937be3b74eb98ddbbc0cd7
Tx public key: 5af8e1d9c4cf718c71a3deb189939eb73904cfa0c7258a3f9691fc3d38f2b642
Timestamp: 1720584205 Timestamp [UCT]: 2024-07-10 04:03:25 Age [y:d:h:m:s]: 00:187:14:06:58
Block: 1062407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134225 RingCT/type: yes/0
Extra: 015af8e1d9c4cf718c71a3deb189939eb73904cfa0c7258a3f9691fc3d38f2b642021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d69d3a16dc6df7c9ab5604451bd6f92b36d46e92c32dbebad65a626415ebd0a9 0.600000000000 1532908 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": 1062417, "vin": [ { "gen": { "height": 1062407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d69d3a16dc6df7c9ab5604451bd6f92b36d46e92c32dbebad65a626415ebd0a9" } } ], "extra": [ 1, 90, 248, 225, 217, 196, 207, 113, 140, 113, 163, 222, 177, 137, 147, 158, 183, 57, 4, 207, 160, 199, 37, 138, 63, 150, 145, 252, 61, 56, 242, 182, 66, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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