Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 420be7eeeffa5c1942694f9a001818a539ff1a95f4db073fd14d57ded57fcbaf

Tx prefix hash: 71c47d1ef632a1e2cb1565e6e820cb05fc32b94ce120ffb5245dce8f6ee211b9
Tx public key: 96a43deaea86949ae8fdf1400a98d009ec4aab2327089c4dbe7e6a2c166e8397
Timestamp: 1695469435 Timestamp [UCT]: 2023-09-23 11:43:55 Age [y:d:h:m:s]: 01:123:23:25:18
Block: 854380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349860 RingCT/type: yes/0
Extra: 0196a43deaea86949ae8fdf1400a98d009ec4aab2327089c4dbe7e6a2c166e8397021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.905908720000 dcy

stealth address amount amount idx
00: 88fe0556f16f2e06dcc53623261c11450d143c7885ebb9f8920725a5afdbc1ba 0.905908720000 1308350 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": 854390, "vin": [ { "gen": { "height": 854380 } } ], "vout": [ { "amount": 905908720, "target": { "key": "88fe0556f16f2e06dcc53623261c11450d143c7885ebb9f8920725a5afdbc1ba" } } ], "extra": [ 1, 150, 164, 61, 234, 234, 134, 148, 154, 232, 253, 241, 64, 10, 152, 208, 9, 236, 74, 171, 35, 39, 8, 156, 77, 190, 126, 106, 44, 22, 110, 131, 151, 2, 17, 0, 0, 0, 8, 230, 210, 127, 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