Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 763e2c2dd2865a19026ad2dbfa10bdadeffe36fce04ce407a93783ac5aa98b7e

Tx prefix hash: c2e33e45783e7ed6ac6076e3ca75e11ca92b1a58f33d2ada592f32e543cd9651
Tx public key: 11343145bedbd7ffb4c592e7179a30785cf5c37c6e0d0dd7d73b4f19c2623819
Timestamp: 1700917326 Timestamp [UCT]: 2023-11-25 13:02:06 Age [y:d:h:m:s]: 02:032:19:28:12
Block: 899359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543256 RingCT/type: yes/0
Extra: 0111343145bedbd7ffb4c592e7179a30785cf5c37c6e0d0dd7d73b4f19c2623819021100000004faf35c9c000000000000000000

1 output(s) for total of 0.642762122000 dcy

stealth address amount amount idx
00: f1c0b214d927fee94b410d63bee0acf17207b35422e871ed78e3005e7578f23e 0.642762122000 1355812 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": 899369, "vin": [ { "gen": { "height": 899359 } } ], "vout": [ { "amount": 642762122, "target": { "key": "f1c0b214d927fee94b410d63bee0acf17207b35422e871ed78e3005e7578f23e" } } ], "extra": [ 1, 17, 52, 49, 69, 190, 219, 215, 255, 180, 197, 146, 231, 23, 154, 48, 120, 92, 245, 195, 124, 110, 13, 13, 215, 215, 59, 79, 25, 194, 98, 56, 25, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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