Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb6e492d9d4addc37bdcf601f3fae98ac66bf225f015620fab44d1823f0ae096

Tx prefix hash: d1d4cb264fed9488c85b0a8ed4f4bc3036e36c24849fbc595c2580487f62df9a
Tx public key: 648fe63db79b4ba4e466afff290a4e0560a906f7788c7fba11a70463d7432b59
Timestamp: 1686453372 Timestamp [UCT]: 2023-06-11 03:16:12 Age [y:d:h:m:s]: 02:150:20:54:31
Block: 779701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 627581 RingCT/type: yes/0
Extra: 01648fe63db79b4ba4e466afff290a4e0560a906f7788c7fba11a70463d7432b5902110000000375e3f0e9000000000000000000

1 output(s) for total of 1.601500495000 dcy

stealth address amount amount idx
00: 1e5dd77afb6ad07be514775ca1a5ed50c4334eb09b0c673f9b12a275ac3764c5 1.601500495000 1229372 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": 779711, "vin": [ { "gen": { "height": 779701 } } ], "vout": [ { "amount": 1601500495, "target": { "key": "1e5dd77afb6ad07be514775ca1a5ed50c4334eb09b0c673f9b12a275ac3764c5" } } ], "extra": [ 1, 100, 143, 230, 61, 183, 155, 75, 164, 228, 102, 175, 255, 41, 10, 78, 5, 96, 169, 6, 247, 120, 140, 127, 186, 17, 167, 4, 99, 215, 67, 43, 89, 2, 17, 0, 0, 0, 3, 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