Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2626970fe6e6a890ab67da72d8138a0687d71bc9e44a40ec655b80558ebe803c

Tx prefix hash: 8f3e1d98b4eb18f06f38c8dfa76161263fb7b240523ffe10cf3cd58a73e346ac
Tx public key: 6f966b05ef9af3cdf65e800be7c69740431479e60ed291a773f13bed4e7e2eac
Timestamp: 1659525065 Timestamp [UCT]: 2022-08-03 11:11:05 Age [y:d:h:m:s]: 02:268:01:44:40
Block: 557772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712824 RingCT/type: yes/0
Extra: 016f966b05ef9af3cdf65e800be7c69740431479e60ed291a773f13bed4e7e2eac0211000000026570b1ef000000000000000000

1 output(s) for total of 8.707028033000 dcy

stealth address amount amount idx
00: a142972f9c0c7b6da985f8fc62e1791b7c8dba0dfd0c73ea19277b90ba8ef520 8.707028033000 989816 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": 557782, "vin": [ { "gen": { "height": 557772 } } ], "vout": [ { "amount": 8707028033, "target": { "key": "a142972f9c0c7b6da985f8fc62e1791b7c8dba0dfd0c73ea19277b90ba8ef520" } } ], "extra": [ 1, 111, 150, 107, 5, 239, 154, 243, 205, 246, 94, 128, 11, 231, 198, 151, 64, 67, 20, 121, 230, 14, 210, 145, 167, 115, 241, 59, 237, 78, 126, 46, 172, 2, 17, 0, 0, 0, 2, 101, 112, 177, 239, 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