Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d65e7f70abe686d4429a0be65c53215d4ec91a8e94d9243d873bb7bac5c1bc1

Tx prefix hash: 4e6f4d4f21ef1ab33b8c7e15415ae1ed0d8126a8f3eec1bb27ae5fd96dcd1809
Tx public key: 0c0c5705ade9743cb52ebef4328e43e695aa6f1742bc99bf23f5ad1f06aed936
Timestamp: 1627697007 Timestamp [UCT]: 2021-07-31 02:03:27 Age [y:d:h:m:s]: 03:268:10:19:59
Block: 304227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 964202 RingCT/type: yes/0
Extra: 010c0c5705ade9743cb52ebef4328e43e695aa6f1742bc99bf23f5ad1f06aed936021100000012e6f80b5a000000000000000000

1 output(s) for total of 60.251816210000 dcy

stealth address amount amount idx
00: bb74a0d98bf1e1c02e51b5218770f64b50700720780739ff90d82f9721dcbd0a 60.251816210000 634812 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": 304237, "vin": [ { "gen": { "height": 304227 } } ], "vout": [ { "amount": 60251816210, "target": { "key": "bb74a0d98bf1e1c02e51b5218770f64b50700720780739ff90d82f9721dcbd0a" } } ], "extra": [ 1, 12, 12, 87, 5, 173, 233, 116, 60, 181, 46, 190, 244, 50, 142, 67, 230, 149, 170, 111, 23, 66, 188, 153, 191, 35, 245, 173, 31, 6, 174, 217, 54, 2, 17, 0, 0, 0, 18, 230, 248, 11, 90, 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