Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b9db7a77b69ca9c33ec6f2236f92da4daa280dafba073fd260c702bb4825e8e

Tx prefix hash: 672d2d001e48fbf4787b699d0f7722f3ab783df40d1f340971880c5a12d37a12
Tx public key: c52d4460d46158f4894ccbde6ad5b0ec5e56dd7d368f93f9ffea838739c5ab05
Timestamp: 1709002884 Timestamp [UCT]: 2024-02-27 03:01:24 Age [y:d:h:m:s]: 01:063:00:48:14
Block: 966394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306075 RingCT/type: yes/0
Extra: 01c52d4460d46158f4894ccbde6ad5b0ec5e56dd7d368f93f9ffea838739c5ab050211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb2809ba2906445c7b553abdd21d3737f02d3e60cd1c508c0ed809de995e43fb 0.600000000000 1426151 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": 966404, "vin": [ { "gen": { "height": 966394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb2809ba2906445c7b553abdd21d3737f02d3e60cd1c508c0ed809de995e43fb" } } ], "extra": [ 1, 197, 45, 68, 96, 212, 97, 88, 244, 137, 76, 203, 222, 106, 213, 176, 236, 94, 86, 221, 125, 54, 143, 147, 249, 255, 234, 131, 135, 57, 197, 171, 5, 2, 17, 0, 0, 0, 2, 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