Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6213dca951a5da18c1a0a756c38c57728bdc95d5716dbc4f8f4078cbc54ced18

Tx prefix hash: 49c932ed29708f2bdd917d60a3071d3fbcc714675a7e5a75dbfe22c56c67d232
Tx public key: b3fcf5ab002bec1e7e3c9ca3b28fefa66812028281dc93f1ad793c0ff8008713
Timestamp: 1702020623 Timestamp [UCT]: 2023-12-08 07:30:23 Age [y:d:h:m:s]: 01:337:11:25:30
Block: 908500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500055 RingCT/type: yes/0
Extra: 01b3fcf5ab002bec1e7e3c9ca3b28fefa66812028281dc93f1ad793c0ff8008713021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01713bc3ba31d0c68c42086e621513a381ef5c9d60de2a4a03abefb463a1f32e 0.600000000000 1365533 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": 908510, "vin": [ { "gen": { "height": 908500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01713bc3ba31d0c68c42086e621513a381ef5c9d60de2a4a03abefb463a1f32e" } } ], "extra": [ 1, 179, 252, 245, 171, 0, 43, 236, 30, 126, 60, 156, 163, 178, 143, 239, 166, 104, 18, 2, 130, 129, 220, 147, 241, 173, 121, 60, 15, 248, 0, 135, 19, 2, 17, 0, 0, 0, 1, 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