Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e8313021410bf4e7af07eb89c012ca80e52e9821085713d9413df408a33da02

Tx prefix hash: 6748422119e9c1167a36cc8f2dacf3618a5eec8b7601cff28737d4453eb4bb6e
Tx public key: ee1baa89bec417af09d041cfd98ff9bcc1c0c4bd8b2641c22410829c92b25e16
Timestamp: 1731470659 Timestamp [UCT]: 2024-11-13 04:04:19 Age [y:d:h:m:s]: 00:148:08:33:43
Block: 1152550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105872 RingCT/type: yes/0
Extra: 01ee1baa89bec417af09d041cfd98ff9bcc1c0c4bd8b2641c22410829c92b25e16021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff2f5c1f331c712158edf5a012a6b8ecc18e3ea095d75b528586a4747f52a430 0.600000000000 1638151 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": 1152560, "vin": [ { "gen": { "height": 1152550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff2f5c1f331c712158edf5a012a6b8ecc18e3ea095d75b528586a4747f52a430" } } ], "extra": [ 1, 238, 27, 170, 137, 190, 196, 23, 175, 9, 208, 65, 207, 217, 143, 249, 188, 193, 192, 196, 189, 139, 38, 65, 194, 36, 16, 130, 156, 146, 178, 94, 22, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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