Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b25504bb4a8c2261016a6cb41e80dd250d67e2e48c45da2c08c9b8184b647ef3

Tx prefix hash: fc664ac407215ac6af3bd0a10b823d247ff0a670fdd5c5fc376b0edfe3bb2d1a
Tx public key: 6dc252d9311a84e60943aeebe10e4158a73f732ea640dd3f7854a41adc47f9a8
Timestamp: 1707922188 Timestamp [UCT]: 2024-02-14 14:49:48 Age [y:d:h:m:s]: 01:040:21:24:02
Block: 957415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290250 RingCT/type: yes/0
Extra: 016dc252d9311a84e60943aeebe10e4158a73f732ea640dd3f7854a41adc47f9a802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a873c65149f74443058fdbbafcee94cc405dcbfa1b30019ac579c073723b93ad 0.600000000000 1416733 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": 957425, "vin": [ { "gen": { "height": 957415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a873c65149f74443058fdbbafcee94cc405dcbfa1b30019ac579c073723b93ad" } } ], "extra": [ 1, 109, 194, 82, 217, 49, 26, 132, 230, 9, 67, 174, 235, 225, 14, 65, 88, 167, 63, 115, 46, 166, 64, 221, 63, 120, 84, 164, 26, 220, 71, 249, 168, 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