Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b2efef04b28829ed0da68831faec8b3ff4aea418bcc20767f2e478a48d61343

Tx prefix hash: a8638b97ddf4db2b877b25a9886972ad68e6a24a0965d36716fe4df3e83d67cd
Tx public key: 1a7c0ca0a03f900e4357deb6f90b7c63716c32f3722d3ba54c2ba3cd9e4ab2ff
Timestamp: 1718768909 Timestamp [UCT]: 2024-06-19 03:48:29 Age [y:d:h:m:s]: 00:287:05:38:13
Block: 1047352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205242 RingCT/type: yes/0
Extra: 011a7c0ca0a03f900e4357deb6f90b7c63716c32f3722d3ba54c2ba3cd9e4ab2ff0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a554ac8ae329f4f2c7924e00339346f30590dda1974be071a48274bb2af87fc6 0.600000000000 1517171 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": 1047362, "vin": [ { "gen": { "height": 1047352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a554ac8ae329f4f2c7924e00339346f30590dda1974be071a48274bb2af87fc6" } } ], "extra": [ 1, 26, 124, 12, 160, 160, 63, 144, 14, 67, 87, 222, 182, 249, 11, 124, 99, 113, 108, 50, 243, 114, 45, 59, 165, 76, 43, 163, 205, 158, 74, 178, 255, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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