Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e17e40922c78ea48f38c8c06a248946f0f2aa33792ad00d6a0fbd99cc5aee6e2

Tx prefix hash: 80940af602da0e809c627493bdf679c374f75acae32c700e0414f2e1d37c1d99
Tx public key: 3fc6965b26880580bbf4272f5ed8c24f6eeed61052048e3bf0034489c5ac5ab3
Timestamp: 1726588956 Timestamp [UCT]: 2024-09-17 16:02:36 Age [y:d:h:m:s]: 00:068:01:38:57
Block: 1112175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48665 RingCT/type: yes/0
Extra: 013fc6965b26880580bbf4272f5ed8c24f6eeed61052048e3bf0034489c5ac5ab3021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acd5f0f33393bcd24b9fb01733bbdd1af65065eccd1c19c1d1a27b510e2aaa49 0.600000000000 1591404 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": 1112185, "vin": [ { "gen": { "height": 1112175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acd5f0f33393bcd24b9fb01733bbdd1af65065eccd1c19c1d1a27b510e2aaa49" } } ], "extra": [ 1, 63, 198, 150, 91, 38, 136, 5, 128, 187, 244, 39, 47, 94, 216, 194, 79, 110, 238, 214, 16, 82, 4, 142, 59, 240, 3, 68, 137, 197, 172, 90, 179, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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