Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fecb231bf3b1a3623155fa4a42fc1e850fde6aab222efafeb2a58e0b014478fb

Tx prefix hash: c9460a3d44a9b1f0d3b711c3d11eb04473ad01a96962a84a4d99cccd80358dfe
Tx public key: 2ee97fcbac861d34b11ed8a2a02c61d65e5a654e30302a551a9b5f9c2c8b1528
Timestamp: 1648368247 Timestamp [UCT]: 2022-03-27 08:04:07 Age [y:d:h:m:s]: 03:222:21:46:09
Block: 467348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 937236 RingCT/type: yes/0
Extra: 012ee97fcbac861d34b11ed8a2a02c61d65e5a654e30302a551a9b5f9c2c8b1528021100000009a8c141c5000000000000000000

1 output(s) for total of 17.357306162000 dcy

stealth address amount amount idx
00: 528ebcbfba2c61d12056fa1c3484cc11f15ca40bf6b77e749238a5bc3945f902 17.357306162000 885835 of 0

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": 467358, "vin": [ { "gen": { "height": 467348 } } ], "vout": [ { "amount": 17357306162, "target": { "key": "528ebcbfba2c61d12056fa1c3484cc11f15ca40bf6b77e749238a5bc3945f902" } } ], "extra": [ 1, 46, 233, 127, 203, 172, 134, 29, 52, 177, 30, 216, 162, 160, 44, 97, 214, 94, 90, 101, 78, 48, 48, 42, 85, 26, 155, 95, 156, 44, 139, 21, 40, 2, 17, 0, 0, 0, 9, 168, 193, 65, 197, 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