Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35b1bc3b2902b9a76a9d50699a37186c8536d24ca450ec86c8ae3150c4539fd5

Tx prefix hash: 971cd1b5ec08e930e46a0340ca77e2328a6586bbb7b7830673f7332b438a414a
Tx public key: a618b32b57c2b8f801b59c9a2e1d7c014ec6b5289d05f5e96e25480bef1d5a43
Timestamp: 1660586406 Timestamp [UCT]: 2022-08-15 18:00:06 Age [y:d:h:m:s]: 02:200:02:51:19
Block: 566548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664221 RingCT/type: yes/0
Extra: 01a618b32b57c2b8f801b59c9a2e1d7c014ec6b5289d05f5e96e25480bef1d5a43021100000002ec6d1a1a000000000000000000

1 output(s) for total of 8.143130575000 dcy

stealth address amount amount idx
00: b28664174b0f08b2bdf5e28970885176ffb20c4f27579eeaf7d67a03251bfbaa 8.143130575000 999542 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": 566558, "vin": [ { "gen": { "height": 566548 } } ], "vout": [ { "amount": 8143130575, "target": { "key": "b28664174b0f08b2bdf5e28970885176ffb20c4f27579eeaf7d67a03251bfbaa" } } ], "extra": [ 1, 166, 24, 179, 43, 87, 194, 184, 248, 1, 181, 156, 154, 46, 29, 124, 1, 78, 198, 181, 40, 157, 5, 245, 233, 110, 37, 72, 11, 239, 29, 90, 67, 2, 17, 0, 0, 0, 2, 236, 109, 26, 26, 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