Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bbeec93e4943633e46b6e72be2810a87d21f4bcb6ae5de4fab29f1729c9ca39

Tx prefix hash: c88d98804c3b00dfc63916031629838dac8e8b610124fa70aa963983de4f2b06
Tx public key: 0c401535c5c41d92721ddb5c4efb1751fe420aadc7f4f835d8244102802a9077
Timestamp: 1723618387 Timestamp [UCT]: 2024-08-14 06:53:07 Age [y:d:h:m:s]: 00:235:15:02:49
Block: 1087562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168261 RingCT/type: yes/0
Extra: 010c401535c5c41d92721ddb5c4efb1751fe420aadc7f4f835d8244102802a907702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d612d2e485a2dca8ba5e225ba97c51f19a32993fbd80170c496a4b2f69af16c7 0.600000000000 1562171 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": 1087572, "vin": [ { "gen": { "height": 1087562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d612d2e485a2dca8ba5e225ba97c51f19a32993fbd80170c496a4b2f69af16c7" } } ], "extra": [ 1, 12, 64, 21, 53, 197, 196, 29, 146, 114, 29, 219, 92, 78, 251, 23, 81, 254, 66, 10, 173, 199, 244, 248, 53, 216, 36, 65, 2, 128, 42, 144, 119, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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