Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63612eda3aa1e3049800da5e67063317202091ab4807f335f845a76de7226518

Tx prefix hash: d823950a3855bf8f613dd4ac38fa92c5f0185bf7d438f7e373e16e94b5f9b01b
Tx public key: 49d01729bed4ca507a6a6fc6bc3db8994f787ca8da8ef7b5dd4fd75cd1d0bc38
Timestamp: 1706312601 Timestamp [UCT]: 2024-01-26 23:43:21 Age [y:d:h:m:s]: 01:294:12:45:25
Block: 944051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469321 RingCT/type: yes/0
Extra: 0149d01729bed4ca507a6a6fc6bc3db8994f787ca8da8ef7b5dd4fd75cd1d0bc3802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3cddc61674a4db660792e1b4983ba18d37e94f087bddc252d9b7a45c6256604 0.600000000000 1402277 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": 944061, "vin": [ { "gen": { "height": 944051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3cddc61674a4db660792e1b4983ba18d37e94f087bddc252d9b7a45c6256604" } } ], "extra": [ 1, 73, 208, 23, 41, 190, 212, 202, 80, 122, 106, 111, 198, 188, 61, 184, 153, 79, 120, 124, 168, 218, 142, 247, 181, 221, 79, 215, 92, 209, 208, 188, 56, 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