Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0d68ff0f22a920486ea14df90ee3ae7c8b0c79940f17e2ed62eec796e7abe7b

Tx prefix hash: f2e524d3176a49ef6f09a3f10e4f32f63c1f750ab5e6e102f06349b1bf91a9e2
Tx public key: d4e62f98c8ad54204e47eb1524836d089e561e385cba2b934e3b384a48eb282a
Timestamp: 1709376179 Timestamp [UCT]: 2024-03-02 10:42:59 Age [y:d:h:m:s]: 01:264:08:40:42
Block: 969486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447670 RingCT/type: yes/0
Extra: 01d4e62f98c8ad54204e47eb1524836d089e561e385cba2b934e3b384a48eb282a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a5bf79c5eb87e7bf658115dc580b6700d800a0ff4b8b3cd1ec9c2f9ccd322f6 0.600000000000 1429319 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": 969496, "vin": [ { "gen": { "height": 969486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a5bf79c5eb87e7bf658115dc580b6700d800a0ff4b8b3cd1ec9c2f9ccd322f6" } } ], "extra": [ 1, 212, 230, 47, 152, 200, 173, 84, 32, 78, 71, 235, 21, 36, 131, 109, 8, 158, 86, 30, 56, 92, 186, 43, 147, 78, 59, 56, 74, 72, 235, 40, 42, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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