Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 043afd3dc5cd024c1a206112926051b791e1f7ae0ea1975785cbbc79479b7323

Tx prefix hash: af4a3522d7a246ca98408f6f2d94924c5f0e30de3d361697788649cdaa0f1393
Tx public key: 8ad3f90314a2ccf00cc5f57fae267e9a97bfaf33583d10ce36458a5c603cff0b
Timestamp: 1726007433 Timestamp [UCT]: 2024-09-10 22:30:33 Age [y:d:h:m:s]: 00:075:00:48:57
Block: 1107366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53644 RingCT/type: yes/0
Extra: 018ad3f90314a2ccf00cc5f57fae267e9a97bfaf33583d10ce36458a5c603cff0b02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bca7137e4f381003b59af55ed49122eeeb2a40b1009557c09ba1e75a7d798c84 0.600000000000 1584977 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": 1107376, "vin": [ { "gen": { "height": 1107366 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bca7137e4f381003b59af55ed49122eeeb2a40b1009557c09ba1e75a7d798c84" } } ], "extra": [ 1, 138, 211, 249, 3, 20, 162, 204, 240, 12, 197, 245, 127, 174, 38, 126, 154, 151, 191, 175, 51, 88, 61, 16, 206, 54, 69, 138, 92, 96, 60, 255, 11, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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