Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e438de3a994b9cbbde9f1ab37be25dc95683828508520f84ec26b91545216d0d

Tx prefix hash: ea20b2c95e66d123d96d83e6a2cc7c67606430045d60da4cc9e82001f04d6f1d
Tx public key: b86082af4001d21213a119d1fafac6ae6133fb5bd9ecdca5468e2ffcbbb58372
Timestamp: 1732860433 Timestamp [UCT]: 2024-11-29 06:07:13 Age [y:d:h:m:s]: 00:115:18:03:59
Block: 1164073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82527 RingCT/type: yes/0
Extra: 01b86082af4001d21213a119d1fafac6ae6133fb5bd9ecdca5468e2ffcbbb583720211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 837c402f090dcdc12e5638b64c305010603fe67263ca6d3b207a1c3a52e8f18d 0.600000000000 1649746 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": 1164083, "vin": [ { "gen": { "height": 1164073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "837c402f090dcdc12e5638b64c305010603fe67263ca6d3b207a1c3a52e8f18d" } } ], "extra": [ 1, 184, 96, 130, 175, 64, 1, 210, 18, 19, 161, 25, 209, 250, 250, 198, 174, 97, 51, 251, 91, 217, 236, 220, 165, 70, 142, 47, 252, 187, 181, 131, 114, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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