Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89de90aa931f551d4444c570746eaa74725c2ac8d2432de04faef401f60d6ddd

Tx prefix hash: 791b008559b07ffaf151d8374bfce43b9bf06ab2ef02887dc376b4c1a2704fd5
Tx public key: af8e4cac59823fcdc161b618288716844f9c84d6dfd4f59104f7aadb79ee186b
Timestamp: 1685606376 Timestamp [UCT]: 2023-06-01 07:59:36 Age [y:d:h:m:s]: 01:274:12:20:32
Block: 772664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457363 RingCT/type: yes/0
Extra: 01af8e4cac59823fcdc161b618288716844f9c84d6dfd4f59104f7aadb79ee186b02110000000275e3f0e9000000000000000000

1 output(s) for total of 1.689832233000 dcy

stealth address amount amount idx
00: 36d8df515be40c1b5ec0e783c4d320dcd29477c915aa5cf7c39836715ca1e308 1.689832233000 1222087 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": 772674, "vin": [ { "gen": { "height": 772664 } } ], "vout": [ { "amount": 1689832233, "target": { "key": "36d8df515be40c1b5ec0e783c4d320dcd29477c915aa5cf7c39836715ca1e308" } } ], "extra": [ 1, 175, 142, 76, 172, 89, 130, 63, 205, 193, 97, 182, 24, 40, 135, 22, 132, 79, 156, 132, 214, 223, 212, 245, 145, 4, 247, 170, 219, 121, 238, 24, 107, 2, 17, 0, 0, 0, 2, 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