Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a60e7ae164bb1d0830018427aad1a1216d1a5e84de0a63cd48be6c3314de4722

Tx prefix hash: b87672a50671f3c1246f5098c913ff751b59d70460e3240738e3c8c38b7ae3b4
Tx public key: b4e46a47931839b247ec9d61162e2c0d0d52bbf2d74ae28de0e454f36bb425d4
Timestamp: 1713973585 Timestamp [UCT]: 2024-04-24 15:46:25 Age [y:d:h:m:s]: 00:306:03:02:16
Block: 1007592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218810 RingCT/type: yes/0
Extra: 01b4e46a47931839b247ec9d61162e2c0d0d52bbf2d74ae28de0e454f36bb425d402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e9d3e5a46bada68a69c5e6f5f7cb6636ffd9aa70776dcec190830bbc107e131 0.600000000000 1468984 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": 1007602, "vin": [ { "gen": { "height": 1007592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e9d3e5a46bada68a69c5e6f5f7cb6636ffd9aa70776dcec190830bbc107e131" } } ], "extra": [ 1, 180, 228, 106, 71, 147, 24, 57, 178, 71, 236, 157, 97, 22, 46, 44, 13, 13, 82, 187, 242, 215, 74, 226, 141, 224, 228, 84, 243, 107, 180, 37, 212, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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