Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab76804bb2ed9e9b33718e1fa75eb23348c9cd7e2e167115c37e68729ca42a7e

Tx prefix hash: efd653886eaa4f77fd0e2dce3d22765bd3556b189a6c7ed171c904055a4f1550
Tx public key: 6925e766f7a8666ffde7b31367f56350b580af3fb8370c11c9159a945c1ce88d
Timestamp: 1700072918 Timestamp [UCT]: 2023-11-15 18:28:38 Age [y:d:h:m:s]: 01:143:03:54:29
Block: 892353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363480 RingCT/type: yes/0
Extra: 016925e766f7a8666ffde7b31367f56350b580af3fb8370c11c9159a945c1ce88d02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.678053672000 dcy

stealth address amount amount idx
00: ffa108426f01256be51e025be4f1a4883e299e846d2882f22d7dca0a228cad5c 0.678053672000 1348472 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": 892363, "vin": [ { "gen": { "height": 892353 } } ], "vout": [ { "amount": 678053672, "target": { "key": "ffa108426f01256be51e025be4f1a4883e299e846d2882f22d7dca0a228cad5c" } } ], "extra": [ 1, 105, 37, 231, 102, 247, 168, 102, 111, 253, 231, 179, 19, 103, 245, 99, 80, 181, 128, 175, 63, 184, 55, 12, 17, 201, 21, 154, 148, 92, 28, 232, 141, 2, 17, 0, 0, 0, 8, 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