Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c554bd544064cf3ce1c76c64c25b1dbf75725f1e511b7015c0482d28c9e546e6

Tx prefix hash: 45b3b6ac4481f9684f3451ddf79d1d28e6131a924116dbb7b8a6142a84771441
Tx public key: 458c3f0149ab8f886b0f5c568a5bd67b34a2d133d4668a67f012b6b20bc45537
Timestamp: 1709307472 Timestamp [UCT]: 2024-03-01 15:37:52 Age [y:d:h:m:s]: 01:251:11:18:55
Block: 968915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438448 RingCT/type: yes/0
Extra: 01458c3f0149ab8f886b0f5c568a5bd67b34a2d133d4668a67f012b6b20bc455370211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 438ff7c368ee1468fa3b16a67c37e301a5543e53747de3615aeeba88abec43f3 0.600000000000 1428742 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": 968925, "vin": [ { "gen": { "height": 968915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "438ff7c368ee1468fa3b16a67c37e301a5543e53747de3615aeeba88abec43f3" } } ], "extra": [ 1, 69, 140, 63, 1, 73, 171, 143, 136, 107, 15, 92, 86, 138, 91, 214, 123, 52, 162, 209, 51, 212, 102, 138, 103, 240, 18, 182, 178, 11, 196, 85, 55, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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