Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 931e5dab4108c3a22478681558fd75b4d9fae5dff66964d34f10c1c9a6f8a03d

Tx prefix hash: cd5a15075cdef685bd7858e51bbce6c912590585e2ddc52cbe81d7116bca00a1
Tx public key: 6d37b58bff117af1f3ee10683cd2da347095d44a33c0bfff521cbaeef16f4a95
Timestamp: 1729827018 Timestamp [UCT]: 2024-10-25 03:30:18 Age [y:d:h:m:s]: 00:030:00:35:56
Block: 1138992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21442 RingCT/type: yes/0
Extra: 016d37b58bff117af1f3ee10683cd2da347095d44a33c0bfff521cbaeef16f4a950211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d313e07486425785259c0378063b024e7f76a3714a3ddee32f58a12ffb7b30a 0.600000000000 1622741 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": 1139002, "vin": [ { "gen": { "height": 1138992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d313e07486425785259c0378063b024e7f76a3714a3ddee32f58a12ffb7b30a" } } ], "extra": [ 1, 109, 55, 181, 139, 255, 17, 122, 241, 243, 238, 16, 104, 60, 210, 218, 52, 112, 149, 212, 74, 51, 192, 191, 255, 82, 28, 186, 238, 241, 111, 74, 149, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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