Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89cf6f5cc410e8c70595207e08516382217ff6a022042c0fdc11ab6a6d1c099b

Tx prefix hash: 771cd42ca76670400a8000976725fe9d315bf66e1e94006d39a6258978455d0f
Tx public key: 00efd05bda181c57da1670e599f05f449a2fcd6783a528d416966091d05cd9ec
Timestamp: 1695612698 Timestamp [UCT]: 2023-09-25 03:31:38 Age [y:d:h:m:s]: 01:259:18:58:47
Block: 855567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446789 RingCT/type: yes/0
Extra: 0100efd05bda181c57da1670e599f05f449a2fcd6783a528d416966091d05cd9ec021100000003faf35c9c000000000000000000

1 output(s) for total of 0.897741733000 dcy

stealth address amount amount idx
00: 6a4dc0e8eb3e7f53738246d001246c7a66c105ec28c536465381271a6c7c5dee 0.897741733000 1309593 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": 855577, "vin": [ { "gen": { "height": 855567 } } ], "vout": [ { "amount": 897741733, "target": { "key": "6a4dc0e8eb3e7f53738246d001246c7a66c105ec28c536465381271a6c7c5dee" } } ], "extra": [ 1, 0, 239, 208, 91, 218, 24, 28, 87, 218, 22, 112, 229, 153, 240, 95, 68, 154, 47, 205, 103, 131, 165, 40, 212, 22, 150, 96, 145, 208, 92, 217, 236, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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