Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c1fda75617c7f81dee8dca6c759664aca6422ac8fcdd41221b8dd274ade2cc0

Tx prefix hash: bcfe1cb580d1ff7b676f564a53aae092391290e94dc4a49cb63ba08d26d88d7c
Tx public key: 99dc1673edb83e79b5d88812bc345b5f424925e8a6178f3c7ab64cdfcaee3ecb
Timestamp: 1696196080 Timestamp [UCT]: 2023-10-01 21:34:40 Age [y:d:h:m:s]: 01:191:14:55:27
Block: 860411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398008 RingCT/type: yes/0
Extra: 0199dc1673edb83e79b5d88812bc345b5f424925e8a6178f3c7ab64cdfcaee3ecb02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.865169548000 dcy

stealth address amount amount idx
00: 68f1d78ee1bddcbfd719d545a0050c4bea6ffc883a37645fbb1dbc7a7318c259 0.865169548000 1314693 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": 860421, "vin": [ { "gen": { "height": 860411 } } ], "vout": [ { "amount": 865169548, "target": { "key": "68f1d78ee1bddcbfd719d545a0050c4bea6ffc883a37645fbb1dbc7a7318c259" } } ], "extra": [ 1, 153, 220, 22, 115, 237, 184, 62, 121, 181, 216, 136, 18, 188, 52, 91, 95, 66, 73, 37, 232, 166, 23, 143, 60, 122, 182, 76, 223, 202, 238, 62, 203, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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