Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2384e3a6e345b6a5f35db8b576feab888ed7724f583ed666d223cb1dcfcebddd

Tx prefix hash: c4d82f0e7e403e95f1d973f0f78d5d8b6204afac7800f8837b979196eda0255b
Tx public key: 3a80882811597f270a424a9c60865cfc8f2862ecb0b03a8a7f1bc3497345f2c3
Timestamp: 1715740142 Timestamp [UCT]: 2024-05-15 02:29:02 Age [y:d:h:m:s]: 01:177:14:26:23
Block: 1022239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385539 RingCT/type: yes/0
Extra: 013a80882811597f270a424a9c60865cfc8f2862ecb0b03a8a7f1bc3497345f2c302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7be4094270221630d19c8bc566388282fc6aeb09aa51d04fc821903e10a952c 0.600000000000 1486780 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": 1022249, "vin": [ { "gen": { "height": 1022239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7be4094270221630d19c8bc566388282fc6aeb09aa51d04fc821903e10a952c" } } ], "extra": [ 1, 58, 128, 136, 40, 17, 89, 127, 39, 10, 66, 74, 156, 96, 134, 92, 252, 143, 40, 98, 236, 176, 176, 58, 138, 127, 27, 195, 73, 115, 69, 242, 195, 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