Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f019500577e92f1b584316b093b2a572e997338fd8e5aa2b5b92df272c2e09

Tx prefix hash: f392fc682dfe88eed42b593e44747cadb788faef298735d7820575c8629d5ca1
Tx public key: 9af3f8fed56143b4eb7737c1c360a7f40f665d02a81361a0a602476da7fb7f1d
Timestamp: 1708861075 Timestamp [UCT]: 2024-02-25 11:37:55 Age [y:d:h:m:s]: 01:070:15:02:09
Block: 965217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311500 RingCT/type: yes/0
Extra: 019af3f8fed56143b4eb7737c1c360a7f40f665d02a81361a0a602476da7fb7f1d02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e28d76aa7c71ad4e317deea25a52debe22ee6b12f69bbfc3d1e80d9cfb73daf 0.600000000000 1424966 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": 965227, "vin": [ { "gen": { "height": 965217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e28d76aa7c71ad4e317deea25a52debe22ee6b12f69bbfc3d1e80d9cfb73daf" } } ], "extra": [ 1, 154, 243, 248, 254, 213, 97, 67, 180, 235, 119, 55, 193, 195, 96, 167, 244, 15, 102, 93, 2, 168, 19, 97, 160, 166, 2, 71, 109, 167, 251, 127, 29, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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