Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f06dbb72e6d6704484671354135ed1aa5fd08f5bc7fef5f38893040eba10b1ae

Tx prefix hash: 2ce7bb0accec6d44e81ac8db1d0dc54313999bcd636301cbdeda63a33be3f037
Tx public key: f2665f48c36838b1d9fb6bd70ad1576a718b2c61984523607f9bad5f46a750f3
Timestamp: 1686533460 Timestamp [UCT]: 2023-06-12 01:31:00 Age [y:d:h:m:s]: 01:338:05:05:17
Block: 780361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502924 RingCT/type: yes/0
Extra: 01f2665f48c36838b1d9fb6bd70ad1576a718b2c61984523607f9bad5f46a750f30211000000044b8f5122000000000000000000

1 output(s) for total of 1.593456538000 dcy

stealth address amount amount idx
00: 34e7addd67cd3ad12691d7bb7ce67509af5390dddc835eb5c8ebc6f328b611e3 1.593456538000 1230064 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": 780371, "vin": [ { "gen": { "height": 780361 } } ], "vout": [ { "amount": 1593456538, "target": { "key": "34e7addd67cd3ad12691d7bb7ce67509af5390dddc835eb5c8ebc6f328b611e3" } } ], "extra": [ 1, 242, 102, 95, 72, 195, 104, 56, 177, 217, 251, 107, 215, 10, 209, 87, 106, 113, 139, 44, 97, 152, 69, 35, 96, 127, 155, 173, 95, 70, 167, 80, 243, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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