Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df4f545f32d3e97b9fb0a06c0ac160070beb4bf867d996fc174b87f2f56e9221

Tx prefix hash: 726d286fb1de20f50545d3d927de0c440a2c2988bc1cb045c8a834db41ea4cde
Tx public key: 8073d33583dda835b618545f9f4960ae97c07c646eac94ca416444bf1882e9a2
Timestamp: 1713353798 Timestamp [UCT]: 2024-04-17 11:36:38 Age [y:d:h:m:s]: 01:029:11:15:37
Block: 1002452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282021 RingCT/type: yes/0
Extra: 018073d33583dda835b618545f9f4960ae97c07c646eac94ca416444bf1882e9a202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e67fdaac90b649163da4d326cd287e99cf0f0c6a05e726d58c537a665019d03 0.600000000000 1462968 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": 1002462, "vin": [ { "gen": { "height": 1002452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e67fdaac90b649163da4d326cd287e99cf0f0c6a05e726d58c537a665019d03" } } ], "extra": [ 1, 128, 115, 211, 53, 131, 221, 168, 53, 182, 24, 84, 95, 159, 73, 96, 174, 151, 192, 124, 100, 110, 172, 148, 202, 65, 100, 68, 191, 24, 130, 233, 162, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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