Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e218b2265d42e6568a6fc0dff5245fc15990997a43d7666d9f20c19c60ed5ecf

Tx prefix hash: 17ab07baa8470fb0295ffa36e527492bad0eb2d0e3b174628c405b7fbd9f7847
Tx public key: 2fb7ad44f3b5bc754a54ca965c91ff0c29ba319ddc55f2985b079840157048a1
Timestamp: 1727104404 Timestamp [UCT]: 2024-09-23 15:13:24 Age [y:d:h:m:s]: 00:203:18:22:04
Block: 1116452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145457 RingCT/type: yes/0
Extra: 012fb7ad44f3b5bc754a54ca965c91ff0c29ba319ddc55f2985b079840157048a1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4e0fae41d76976ed5a28aa3c21a822622e20b61352e3fb7301af8dad1c7985b 0.600000000000 1596939 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": 1116462, "vin": [ { "gen": { "height": 1116452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4e0fae41d76976ed5a28aa3c21a822622e20b61352e3fb7301af8dad1c7985b" } } ], "extra": [ 1, 47, 183, 173, 68, 243, 181, 188, 117, 74, 84, 202, 150, 92, 145, 255, 12, 41, 186, 49, 157, 220, 85, 242, 152, 91, 7, 152, 64, 21, 112, 72, 161, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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