Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d987ac500a59e8cc5becf36ef870867cabae09fbc4c2af75ef2a7d72574edb25

Tx prefix hash: 286c23846dc06b6a7f37cd29b7c714693f255588a11d9fb8cec8185a26043abd
Tx public key: 337f6f33ca0b411ec52e6e37e9f257fb512831a8aad532c9b4e4cfaa6947ac65
Timestamp: 1738620686 Timestamp [UCT]: 2025-02-03 22:11:26 Age [y:d:h:m:s]: 00:290:19:39:10
Block: 1211493 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205612 RingCT/type: yes/0
Extra: 01337f6f33ca0b411ec52e6e37e9f257fb512831a8aad532c9b4e4cfaa6947ac650211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6726ff2f321fd38c1705958a9cea4625a9c9ac75280a855347761064c0fa15e2 0.600000000000 1698254 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": 1211503, "vin": [ { "gen": { "height": 1211493 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6726ff2f321fd38c1705958a9cea4625a9c9ac75280a855347761064c0fa15e2" } } ], "extra": [ 1, 51, 127, 111, 51, 202, 11, 65, 30, 197, 46, 110, 55, 233, 242, 87, 251, 81, 40, 49, 168, 170, 213, 50, 201, 180, 228, 207, 170, 105, 71, 172, 101, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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