Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08909730981e42c26d868e281825a331ab91dca1f0413e80ffc546ff8b934e97

Tx prefix hash: 83a6a1f6f6bf0b62bf5137b66639593be5c2491d5f803fe0dc732f1c8ee5e7c3
Tx public key: b02aab9e64530071e828bdf27dd177be47ebeb54d1ee8925094c605a4a70b039
Timestamp: 1700762509 Timestamp [UCT]: 2023-11-23 18:01:49 Age [y:d:h:m:s]: 01:126:00:11:39
Block: 898068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351220 RingCT/type: yes/0
Extra: 01b02aab9e64530071e828bdf27dd177be47ebeb54d1ee8925094c605a4a70b03902110000000d75e3f0e9000000000000000000

1 output(s) for total of 0.649124344000 dcy

stealth address amount amount idx
00: 8d78ef5a230e9cb868bc3aacbf6a51ead2dc3f7e32ad015c12baf55cc23e5a5c 0.649124344000 1354471 of 0

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": 898078, "vin": [ { "gen": { "height": 898068 } } ], "vout": [ { "amount": 649124344, "target": { "key": "8d78ef5a230e9cb868bc3aacbf6a51ead2dc3f7e32ad015c12baf55cc23e5a5c" } } ], "extra": [ 1, 176, 42, 171, 158, 100, 83, 0, 113, 232, 40, 189, 242, 125, 209, 119, 190, 71, 235, 235, 84, 209, 238, 137, 37, 9, 76, 96, 90, 74, 112, 176, 57, 2, 17, 0, 0, 0, 13, 117, 227, 240, 233, 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