Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21020bc192af9224debca1107502d09a5cfe0464d13e456c0bada03e2f258dc2

Tx prefix hash: c3e39af7d3ce2e59cceb49a4c1b6a3b772063a2219602d74287262c921e8dd41
Tx public key: 568d048bc8ec59310154f77c184843de0c2f53f513c9153eee66c191fb1e5203
Timestamp: 1709769294 Timestamp [UCT]: 2024-03-06 23:54:54 Age [y:d:h:m:s]: 00:266:14:27:09
Block: 972744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190868 RingCT/type: yes/0
Extra: 01568d048bc8ec59310154f77c184843de0c2f53f513c9153eee66c191fb1e52030211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45331c9204e5bc5cf6f2d411c1f9ba17e0bb9f47a2283c4d408687283ed288c8 0.600000000000 1432663 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": 972754, "vin": [ { "gen": { "height": 972744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45331c9204e5bc5cf6f2d411c1f9ba17e0bb9f47a2283c4d408687283ed288c8" } } ], "extra": [ 1, 86, 141, 4, 139, 200, 236, 89, 49, 1, 84, 247, 124, 24, 72, 67, 222, 12, 47, 83, 245, 19, 201, 21, 62, 238, 102, 193, 145, 251, 30, 82, 3, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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