Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f288a2ab0d07b96be8ffb7fc0a5e69dc490af1e68c413683b01e8ebb862a8b46

Tx prefix hash: 22e5023fc57004a9a077754ddf2ef5c77fc0cf858a5f9f6cb1fc1cbb47bdfc02
Tx public key: a0e7ce82026e1f8dd36ee53246762a198e7b3f6af637fe974ec36b48770058b8
Timestamp: 1681987289 Timestamp [UCT]: 2023-04-20 10:41:29 Age [y:d:h:m:s]: 01:267:23:56:32
Block: 742657 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453033 RingCT/type: yes/0
Extra: 01a0e7ce82026e1f8dd36ee53246762a198e7b3f6af637fe974ec36b48770058b8021100000004e7ace25d000000000000000000

1 output(s) for total of 2.124561373000 dcy

stealth address amount amount idx
00: 1fcb89aab0ff4e549cc353f2adc3f0ce69d319c1fc91942a0264fad23cfd14ec 2.124561373000 1189634 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": 742667, "vin": [ { "gen": { "height": 742657 } } ], "vout": [ { "amount": 2124561373, "target": { "key": "1fcb89aab0ff4e549cc353f2adc3f0ce69d319c1fc91942a0264fad23cfd14ec" } } ], "extra": [ 1, 160, 231, 206, 130, 2, 110, 31, 141, 211, 110, 229, 50, 70, 118, 42, 25, 142, 123, 63, 106, 246, 55, 254, 151, 78, 195, 107, 72, 119, 0, 88, 184, 2, 17, 0, 0, 0, 4, 231, 172, 226, 93, 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