Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eb3440b0e8ba4ae75ae3b3e963fcb6dbff480c577e4d18fa0cfae8daf488d4a

Tx prefix hash: e4525b4f7808f1cabf8128548c908dce79ab46a82444c28d7b744bf0e8adfb08
Tx public key: f681404d9d4f3645675511845175e11928a5517a2e1295dc38024951d519678f
Timestamp: 1703568864 Timestamp [UCT]: 2023-12-26 05:34:24 Age [y:d:h:m:s]: 01:140:08:43:09
Block: 921334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361467 RingCT/type: yes/0
Extra: 01f681404d9d4f3645675511845175e11928a5517a2e1295dc38024951d519678f0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06654a9ee614fd3fd19f0a27568cbe410b3fc06f7bb47747bb3ae605a7a9811e 0.600000000000 1379020 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": 921344, "vin": [ { "gen": { "height": 921334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06654a9ee614fd3fd19f0a27568cbe410b3fc06f7bb47747bb3ae605a7a9811e" } } ], "extra": [ 1, 246, 129, 64, 77, 157, 79, 54, 69, 103, 85, 17, 132, 81, 117, 225, 25, 40, 165, 81, 122, 46, 18, 149, 220, 56, 2, 73, 81, 213, 25, 103, 143, 2, 17, 0, 0, 0, 3, 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