Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a568e7a331a7d4423a7745aa5f4358e59a9cc25fbad7b40cdd88157d93c0247

Tx prefix hash: 760f62bdbe24d36992faa210ba9fdb96ad25022a460c29cdd570788aa478c57a
Tx public key: 135d1eac359f4f5282011513d4e7bd7694e7d5a6203163b0aa924257d9e1d3c5
Timestamp: 1681033794 Timestamp [UCT]: 2023-04-09 09:49:54 Age [y:d:h:m:s]: 01:363:15:34:51
Block: 734764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521163 RingCT/type: yes/0
Extra: 01135d1eac359f4f5282011513d4e7bd7694e7d5a6203163b0aa924257d9e1d3c5021100000002b3164c24000000000000000000

1 output(s) for total of 2.256431108000 dcy

stealth address amount amount idx
00: 1fffd0996538605e93cb867636f7259a182a859f4350ca49f42277d68d89e97f 2.256431108000 1181015 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": 734774, "vin": [ { "gen": { "height": 734764 } } ], "vout": [ { "amount": 2256431108, "target": { "key": "1fffd0996538605e93cb867636f7259a182a859f4350ca49f42277d68d89e97f" } } ], "extra": [ 1, 19, 93, 30, 172, 53, 159, 79, 82, 130, 1, 21, 19, 212, 231, 189, 118, 148, 231, 213, 166, 32, 49, 99, 176, 170, 146, 66, 87, 217, 225, 211, 197, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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