Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340378fdc937c5ae4a7e05ce8904cc6ff0624edfb6d34f04bce413f07db949b2

Tx prefix hash: 50c864c20915417a2e26609bc2aac141a6034aae107b0f16358d6349f58e6cb8
Tx public key: 60711687c9b4e026d8301a029bb576aee5eaa1b15445e989db9f74a47e572d28
Timestamp: 1723078469 Timestamp [UCT]: 2024-08-08 00:54:29 Age [y:d:h:m:s]: 01:104:07:07:00
Block: 1083074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333033 RingCT/type: yes/0
Extra: 0160711687c9b4e026d8301a029bb576aee5eaa1b15445e989db9f74a47e572d2802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0abfbfcd8863415c095666e1d5df82520cc1700f51690aa695c0b68e864d28f 0.600000000000 1556909 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": 1083084, "vin": [ { "gen": { "height": 1083074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0abfbfcd8863415c095666e1d5df82520cc1700f51690aa695c0b68e864d28f" } } ], "extra": [ 1, 96, 113, 22, 135, 201, 180, 224, 38, 216, 48, 26, 2, 155, 181, 118, 174, 229, 234, 161, 177, 84, 69, 233, 137, 219, 159, 116, 164, 126, 87, 45, 40, 2, 17, 0, 0, 0, 1, 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