Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06bc9f6fa42adf64a6fa6311f90281b2cf3da9bea77a91a1dbc50605e9f54202

Tx prefix hash: 3f0cbaff9948f6e1e891fa5ae933c9d9437ef25fe681bc8201211bf1998edbdc
Tx public key: f8d7596eee5b81fe2d51376a10e02d6298c24e67658bac0edc7621fbde53c970
Timestamp: 1735278769 Timestamp [UCT]: 2024-12-27 05:52:49 Age [y:d:h:m:s]: 00:083:21:42:33
Block: 1184096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59769 RingCT/type: yes/0
Extra: 01f8d7596eee5b81fe2d51376a10e02d6298c24e67658bac0edc7621fbde53c9700211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0caf1d87c95b4a93ee6dc75ed76eb42db4ef5415b1f44445af5187457e0c2cd 0.600000000000 1670549 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": 1184106, "vin": [ { "gen": { "height": 1184096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0caf1d87c95b4a93ee6dc75ed76eb42db4ef5415b1f44445af5187457e0c2cd" } } ], "extra": [ 1, 248, 215, 89, 110, 238, 91, 129, 254, 45, 81, 55, 106, 16, 224, 45, 98, 152, 194, 78, 103, 101, 139, 172, 14, 220, 118, 33, 251, 222, 83, 201, 112, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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