Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10efbe01f7449f00530a284ec0ff12df42cea19f302164bb410cafcd90167621

Tx prefix hash: c9c8699b0498b724b788a5798b9be5b0994272d9587782f87ee84310c06f1de9
Tx public key: c4e88b5de340109659c20282b9a1011445e3472b8f04c9f000a93f72e029d44c
Timestamp: 1699749607 Timestamp [UCT]: 2023-11-12 00:40:07 Age [y:d:h:m:s]: 01:362:04:36:46
Block: 889672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 517766 RingCT/type: yes/0
Extra: 01c4e88b5de340109659c20282b9a1011445e3472b8f04c9f000a93f72e029d44c02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.692065727000 dcy

stealth address amount amount idx
00: 199ed715764220d9f68dcc02ddb28cb7183d1fff1f138d8a0bfd34b7b70b9a29 0.692065727000 1345681 of 0

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": 889682, "vin": [ { "gen": { "height": 889672 } } ], "vout": [ { "amount": 692065727, "target": { "key": "199ed715764220d9f68dcc02ddb28cb7183d1fff1f138d8a0bfd34b7b70b9a29" } } ], "extra": [ 1, 196, 232, 139, 93, 227, 64, 16, 150, 89, 194, 2, 130, 185, 161, 1, 20, 69, 227, 71, 43, 143, 4, 201, 240, 0, 169, 63, 114, 224, 41, 212, 76, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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