Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0f215b5e06cfcee7e38de083ee02c9a1ab9ab8a0c125c00c659d65e5bbcaa70

Tx prefix hash: 89a3c53d401ac6362ce5a117759575f0f7ec25b1ac45cda771a69eaee12ab14d
Tx public key: 5390befa79b42b8ef3c65976813dfe5f7d5b6fca1a5982be8e37b92ba3388028
Timestamp: 1718425485 Timestamp [UCT]: 2024-06-15 04:24:45 Age [y:d:h:m:s]: 00:274:09:04:19
Block: 1044510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196080 RingCT/type: yes/0
Extra: 015390befa79b42b8ef3c65976813dfe5f7d5b6fca1a5982be8e37b92ba338802802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bacc66815788344bf76c93614c02cbaae773dc8407bda6d6f236b46c2a19fe22 0.600000000000 1513837 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": 1044520, "vin": [ { "gen": { "height": 1044510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bacc66815788344bf76c93614c02cbaae773dc8407bda6d6f236b46c2a19fe22" } } ], "extra": [ 1, 83, 144, 190, 250, 121, 180, 43, 142, 243, 198, 89, 118, 129, 61, 254, 95, 125, 91, 111, 202, 26, 89, 130, 190, 142, 55, 185, 43, 163, 56, 128, 40, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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