Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f270c6370f44d6e0df6445e2235e602e053c20ab12eb456487d0166d66758e60

Tx prefix hash: 62d49adaf6a4b56732db078a3e0f5df61b5fcabb85f0a05fa70d55543d5ddf2c
Tx public key: ed1827eb6a3f1532e787910db32bb1c1a4ea8a68477e6fa5bbd6733bde6eac1e
Timestamp: 1736568360 Timestamp [UCT]: 2025-01-11 04:06:00 Age [y:d:h:m:s]: 00:160:11:46:05
Block: 1194772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114375 RingCT/type: yes/0
Extra: 01ed1827eb6a3f1532e787910db32bb1c1a4ea8a68477e6fa5bbd6733bde6eac1e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0517ef50f99c7d5ae3b9856393a241925ee078145cb788466cf3d88d6a1d9ede 0.600000000000 1681349 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": 1194782, "vin": [ { "gen": { "height": 1194772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0517ef50f99c7d5ae3b9856393a241925ee078145cb788466cf3d88d6a1d9ede" } } ], "extra": [ 1, 237, 24, 39, 235, 106, 63, 21, 50, 231, 135, 145, 13, 179, 43, 177, 193, 164, 234, 138, 104, 71, 126, 111, 165, 187, 214, 115, 59, 222, 110, 172, 30, 2, 17, 0, 0, 0, 2, 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