Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1890e3b65afe672aa79c309ce097467de89d1ee28d56b62256c7b3e45e8e35e1

Tx prefix hash: 607a6698030a623af6128f624c99cdd0901900a2d2285ea776eb517db9525d00
Tx public key: bed475d3525f3860dc5e4b81a7d6d26c83b3903046c01d253bb180a7ae95fcd7
Timestamp: 1729470995 Timestamp [UCT]: 2024-10-21 00:36:35 Age [y:d:h:m:s]: 00:187:18:20:24
Block: 1136044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134020 RingCT/type: yes/0
Extra: 01bed475d3525f3860dc5e4b81a7d6d26c83b3903046c01d253bb180a7ae95fcd7021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 175e6e3ed1e184cf4eef974c93a29d1f39c5077b3b20461886ce58145e04b69d 0.600000000000 1619387 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": 1136054, "vin": [ { "gen": { "height": 1136044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "175e6e3ed1e184cf4eef974c93a29d1f39c5077b3b20461886ce58145e04b69d" } } ], "extra": [ 1, 190, 212, 117, 211, 82, 95, 56, 96, 220, 94, 75, 129, 167, 214, 210, 108, 131, 179, 144, 48, 70, 192, 29, 37, 59, 177, 128, 167, 174, 149, 252, 215, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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