Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bb99b6ff40ebac82994d22ad512e48d3ddfb3c941b4546016cbf93b8c494b88

Tx prefix hash: 0be93aa053d4a3730fd783746919e0cebfa2f274df3968ae0e47776399a5a8d4
Tx public key: 43061be62d649f80d629ffbd85c2ae061e993ae36ef7ff935a7670081ba2158e
Timestamp: 1722539347 Timestamp [UCT]: 2024-08-01 19:09:07 Age [y:d:h:m:s]: 00:115:06:59:24
Block: 1078598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82491 RingCT/type: yes/0
Extra: 0143061be62d649f80d629ffbd85c2ae061e993ae36ef7ff935a7670081ba2158e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4345c3b04aded82de3c1c05e415de604708958b5730e9f08a5eaeabd4323bf18 0.600000000000 1551199 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": 1078608, "vin": [ { "gen": { "height": 1078598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4345c3b04aded82de3c1c05e415de604708958b5730e9f08a5eaeabd4323bf18" } } ], "extra": [ 1, 67, 6, 27, 230, 45, 100, 159, 128, 214, 41, 255, 189, 133, 194, 174, 6, 30, 153, 58, 227, 110, 247, 255, 147, 90, 118, 112, 8, 27, 162, 21, 142, 2, 17, 0, 0, 0, 9, 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