Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae294d5bfc9b82779576813bf49870e517c7dd31ae095fd07bb59954a1607330

Tx prefix hash: f402b310be4f7ba91140dc857cbbd90a4d7ed58880406cd3ba8e5cf2f0c41796
Tx public key: f712da95554006fe3c1ca017979e2e106d73d612ed913ef4480a6b7ae153d4cb
Timestamp: 1718788149 Timestamp [UCT]: 2024-06-19 09:09:09 Age [y:d:h:m:s]: 01:137:17:55:00
Block: 1047512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356991 RingCT/type: yes/0
Extra: 01f712da95554006fe3c1ca017979e2e106d73d612ed913ef4480a6b7ae153d4cb0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76419174fbbaaf268f51c73f2a55e78980cc07a2dac363b7edf5d188ee39ab89 0.600000000000 1517355 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": 1047522, "vin": [ { "gen": { "height": 1047512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76419174fbbaaf268f51c73f2a55e78980cc07a2dac363b7edf5d188ee39ab89" } } ], "extra": [ 1, 247, 18, 218, 149, 85, 64, 6, 254, 60, 28, 160, 23, 151, 158, 46, 16, 109, 115, 214, 18, 237, 145, 62, 244, 72, 10, 107, 122, 225, 83, 212, 203, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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