Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9df1a3573e7ef312b172d25a4356f1043e0eedf9e355d01757265a4f0ca92e7

Tx prefix hash: f2ba95773073121da8cda8a8b94f5124258520a8d09a953a519752ddc0c3f897
Tx public key: 294279af68b72eb3b4f201340a18498e3d4facf9544293f6ebcf38ce5cf0e7ad
Timestamp: 1705798898 Timestamp [UCT]: 2024-01-21 01:01:38 Age [y:d:h:m:s]: 01:083:19:31:43
Block: 939781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321024 RingCT/type: yes/0
Extra: 01294279af68b72eb3b4f201340a18498e3d4facf9544293f6ebcf38ce5cf0e7ad0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8136ad8f57c26c87a2d38b438c5709ab0d5db4b9f35442c599b0a77496d8f57a 0.600000000000 1397913 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": 939791, "vin": [ { "gen": { "height": 939781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8136ad8f57c26c87a2d38b438c5709ab0d5db4b9f35442c599b0a77496d8f57a" } } ], "extra": [ 1, 41, 66, 121, 175, 104, 183, 46, 179, 180, 242, 1, 52, 10, 24, 73, 142, 61, 79, 172, 249, 84, 66, 147, 246, 235, 207, 56, 206, 92, 240, 231, 173, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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