Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba24c959f99c623fc6623c521d5058554ffabc5c99f06b82e0d7bbe1d0352de6

Tx prefix hash: 90d93a5bb07edb48ec30d2d6b84c82e73cdcdb01edbb23a6bba0e564b8a82837
Tx public key: aeb805a17f2c8ea672b1c30addf6e12a55faaabef4543fcc1e02e20a7913c0ea
Timestamp: 1711586723 Timestamp [UCT]: 2024-03-28 00:45:23 Age [y:d:h:m:s]: 01:008:15:16:34
Block: 987824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267119 RingCT/type: yes/0
Extra: 01aeb805a17f2c8ea672b1c30addf6e12a55faaabef4543fcc1e02e20a7913c0ea02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93cbb9bc56dc97cc0d29aaf44cadf0e240e59eac09bcc4a85a132b0ee6e2485c 0.600000000000 1448083 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": 987834, "vin": [ { "gen": { "height": 987824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93cbb9bc56dc97cc0d29aaf44cadf0e240e59eac09bcc4a85a132b0ee6e2485c" } } ], "extra": [ 1, 174, 184, 5, 161, 127, 44, 142, 166, 114, 177, 195, 10, 221, 246, 225, 42, 85, 250, 170, 190, 244, 84, 63, 204, 30, 2, 226, 10, 121, 19, 192, 234, 2, 17, 0, 0, 0, 1, 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