Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b522cd77e0c8a591f3a9f28c5a70e1377810d735ad50edaaa1c36e5191b7574d

Tx prefix hash: 609c2885407c001746869f0a66c4fe44a70f6399507359c82759775f514c7722
Tx public key: f5fc5d7271b6d075c4f0a1d0764b15e0491767a2088b634d5745369723f625d6
Timestamp: 1733154907 Timestamp [UCT]: 2024-12-02 15:55:07 Age [y:d:h:m:s]: 00:202:20:02:19
Block: 1166516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144608 RingCT/type: yes/0
Extra: 01f5fc5d7271b6d075c4f0a1d0764b15e0491767a2088b634d5745369723f625d6021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1670821c68c8ec8099b84b1f855e5acde0c2a524aa1e2f777ec677ac20b57c46 0.600000000000 1652203 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": 1166526, "vin": [ { "gen": { "height": 1166516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1670821c68c8ec8099b84b1f855e5acde0c2a524aa1e2f777ec677ac20b57c46" } } ], "extra": [ 1, 245, 252, 93, 114, 113, 182, 208, 117, 196, 240, 161, 208, 118, 75, 21, 224, 73, 23, 103, 162, 8, 139, 99, 77, 87, 69, 54, 151, 35, 246, 37, 214, 2, 17, 0, 0, 0, 9, 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