Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b0307a605798591e7989ff55a4e7fd9f0c057f977569d28c94588e9489a357

Tx prefix hash: 5ec31433b315b5dcb65fffd4e7cfdbadab3cdba0519ca82985dad5d47e477ac2
Tx public key: 75295e91419e507877c855f997e94c6ec4f97a1514e933b02b11376b309b7036
Timestamp: 1712284822 Timestamp [UCT]: 2024-04-05 02:40:22 Age [y:d:h:m:s]: 00:326:09:18:37
Block: 993573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233343 RingCT/type: yes/0
Extra: 0175295e91419e507877c855f997e94c6ec4f97a1514e933b02b11376b309b70360211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 973d9f61856d1c9631f4fd2dc78b0bf5899ce4aa1deda4f6d8955e1af2899f97 0.600000000000 1453959 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": 993583, "vin": [ { "gen": { "height": 993573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "973d9f61856d1c9631f4fd2dc78b0bf5899ce4aa1deda4f6d8955e1af2899f97" } } ], "extra": [ 1, 117, 41, 94, 145, 65, 158, 80, 120, 119, 200, 85, 249, 151, 233, 76, 110, 196, 249, 122, 21, 20, 233, 51, 176, 43, 17, 55, 107, 48, 155, 112, 54, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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