Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03eb6604490ef92da22e14f5983c6a26ec149be711dbac4d59789cc97353e0f

Tx prefix hash: 30dcd37037f5b998cec4dd98d8ff4d92fcd6a74f6a1ce79f554831f3d34e9da3
Tx public key: e8fcb9042a7631128356fa53f4006e54bc207d3383b70a4cba7b3aabcb636aea
Timestamp: 1716455319 Timestamp [UCT]: 2024-05-23 09:08:39 Age [y:d:h:m:s]: 00:233:08:34:25
Block: 1028175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167002 RingCT/type: yes/0
Extra: 01e8fcb9042a7631128356fa53f4006e54bc207d3383b70a4cba7b3aabcb636aea02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6b3b4e4d4aa61fa89313c7aff2d040314ee9661f8a97f05b92d87f61687cfb5 0.600000000000 1496124 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": 1028185, "vin": [ { "gen": { "height": 1028175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6b3b4e4d4aa61fa89313c7aff2d040314ee9661f8a97f05b92d87f61687cfb5" } } ], "extra": [ 1, 232, 252, 185, 4, 42, 118, 49, 18, 131, 86, 250, 83, 244, 0, 110, 84, 188, 32, 125, 51, 131, 183, 10, 76, 186, 123, 58, 171, 203, 99, 106, 234, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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