Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0c6e3a5b3df314deb9b989955fec164e4888c7bf0764ce0127a761f4015c950

Tx prefix hash: 57223ec58d8edaa81c958beb3310ee18a142c0e44c1f667ba092ef621379759c
Tx public key: a1afc38b3d8671ba1b5ef82a6c303347af9313f9507bf6551403e71358deac01
Timestamp: 1577259732 Timestamp [UCT]: 2019-12-25 07:42:12 Age [y:d:h:m:s]: 05:070:16:18:47
Block: 31236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200346 RingCT/type: yes/0
Extra: 01a1afc38b3d8671ba1b5ef82a6c303347af9313f9507bf6551403e71358deac010211000000084ac5aa02000000000000000000

1 output(s) for total of 483.659623733000 dcy

stealth address amount amount idx
00: 7e23428c5e7c2a1488b09f181d54b023f8000ea4b4ae5d5a64e26fa481d3bb28 483.659623733000 51642 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": 31246, "vin": [ { "gen": { "height": 31236 } } ], "vout": [ { "amount": 483659623733, "target": { "key": "7e23428c5e7c2a1488b09f181d54b023f8000ea4b4ae5d5a64e26fa481d3bb28" } } ], "extra": [ 1, 161, 175, 195, 139, 61, 134, 113, 186, 27, 94, 248, 42, 108, 48, 51, 71, 175, 147, 19, 249, 80, 123, 246, 85, 20, 3, 231, 19, 88, 222, 172, 1, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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