Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6a8e676e2b7c63777c49c1d150a007d9ad4b335d140407e76dbda4c9e5d0fa2

Tx prefix hash: 5626894c59c0dd6a2a25cd3fcbbdc2ddb7c251b82afe77ae76e6198da7538ea9
Tx public key: 55fb625da550a0f7aa14bd8d18b32bd7f864c6a5e8e6b4a69274a63bbb8c6c36
Timestamp: 1733790143 Timestamp [UCT]: 2024-12-10 00:22:23 Age [y:d:h:m:s]: 00:106:04:28:26
Block: 1171778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75660 RingCT/type: yes/0
Extra: 0155fb625da550a0f7aa14bd8d18b32bd7f864c6a5e8e6b4a69274a63bbb8c6c360211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56a49aba9431c871e6cd658fd53850ef93845c81557c23bbd0379cb2b51dc818 0.600000000000 1657579 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": 1171788, "vin": [ { "gen": { "height": 1171778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56a49aba9431c871e6cd658fd53850ef93845c81557c23bbd0379cb2b51dc818" } } ], "extra": [ 1, 85, 251, 98, 93, 165, 80, 160, 247, 170, 20, 189, 141, 24, 179, 43, 215, 248, 100, 198, 165, 232, 230, 180, 166, 146, 116, 166, 59, 187, 140, 108, 54, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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