Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b70ad36266739e90657f695104abd332f32da68fcff23fb2bff9b5f17d3142d9

Tx prefix hash: b9f34c4f5248f358f443b853260630d5418e7ff89c92639f1a6a847f60a43d15
Tx public key: f5af6ec150d15d4474fe627b7cab2be59a3ff9f26eb6800b89225c4140d3ad7f
Timestamp: 1733846265 Timestamp [UCT]: 2024-12-10 15:57:45 Age [y:d:h:m:s]: 00:101:07:50:56
Block: 1172253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72196 RingCT/type: yes/0
Extra: 01f5af6ec150d15d4474fe627b7cab2be59a3ff9f26eb6800b89225c4140d3ad7f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae0e026244ab86b56fa85708d62d1a01a12272b74ab6d8b03e8db90cd9f4ae58 0.600000000000 1658122 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": 1172263, "vin": [ { "gen": { "height": 1172253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae0e026244ab86b56fa85708d62d1a01a12272b74ab6d8b03e8db90cd9f4ae58" } } ], "extra": [ 1, 245, 175, 110, 193, 80, 209, 93, 68, 116, 254, 98, 123, 124, 171, 43, 229, 154, 63, 249, 242, 110, 182, 128, 11, 137, 34, 92, 65, 64, 211, 173, 127, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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