Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a761016db29b2498cfe623756027472de501881920accb050a852c210918a0d

Tx prefix hash: 8b3d14beeb0250d169338c588d79604e87623f14a7d7f5bb6c60be304455c786
Tx public key: 5b53a4d3f9291a4ed40a57dcb86532866bf973aeaf5f5e9ba9b39cf9a3e67bb0
Timestamp: 1674640986 Timestamp [UCT]: 2023-01-25 10:03:06 Age [y:d:h:m:s]: 01:352:23:13:17
Block: 682389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513256 RingCT/type: yes/0
Extra: 015b53a4d3f9291a4ed40a57dcb86532866bf973aeaf5f5e9ba9b39cf9a3e67bb0021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.364820559000 dcy

stealth address amount amount idx
00: 5337e1f18ae82c0d3257cee60856c55675d1776de22873e6e06fa2628d5ac964 3.364820559000 1124508 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": 682399, "vin": [ { "gen": { "height": 682389 } } ], "vout": [ { "amount": 3364820559, "target": { "key": "5337e1f18ae82c0d3257cee60856c55675d1776de22873e6e06fa2628d5ac964" } } ], "extra": [ 1, 91, 83, 164, 211, 249, 41, 26, 78, 212, 10, 87, 220, 184, 101, 50, 134, 107, 249, 115, 174, 175, 95, 94, 155, 169, 179, 156, 249, 163, 230, 123, 176, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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