Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b944b4ce149307d37e8c4f37c094f4459421689f46d31d4bb9f646d8c9dab5d

Tx prefix hash: e815e0c528c74d69ff75e2924d2d103f0ba1279e323740fa2e9a07a8a96565df
Tx public key: 384b35ba7274b929650fe5d04d38bbe4fdbc29b794b23048015b35b087824d51
Timestamp: 1723706675 Timestamp [UCT]: 2024-08-15 07:24:35 Age [y:d:h:m:s]: 01:077:06:40:01
Block: 1088291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313686 RingCT/type: yes/0
Extra: 01384b35ba7274b929650fe5d04d38bbe4fdbc29b794b23048015b35b087824d51021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a12ba50c3befa3deaad8a63813c8e5fd3ddc0c7ba7c1e65a1a8ebbeaacd5034b 0.600000000000 1562906 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": 1088301, "vin": [ { "gen": { "height": 1088291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a12ba50c3befa3deaad8a63813c8e5fd3ddc0c7ba7c1e65a1a8ebbeaacd5034b" } } ], "extra": [ 1, 56, 75, 53, 186, 114, 116, 185, 41, 101, 15, 229, 208, 77, 56, 187, 228, 253, 188, 41, 183, 148, 178, 48, 72, 1, 91, 53, 176, 135, 130, 77, 81, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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