Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b557a600404186ae5109304d646e2bea2f90663b8a8ce64958b0ea0f60eba06a

Tx prefix hash: 71260a4982b32fd41f58d7849849043b42d3a002da106dbc4b872de57414f8cd
Tx public key: 361afb4d851689f3e37b75b49d9d555c9c1eb7c171933c65f841d9695f9f88b8
Timestamp: 1681155270 Timestamp [UCT]: 2023-04-10 19:34:30 Age [y:d:h:m:s]: 02:007:02:36:41
Block: 735750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527248 RingCT/type: yes/0
Extra: 01361afb4d851689f3e37b75b49d9d555c9c1eb7c171933c65f841d9695f9f88b8021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.239520538000 dcy

stealth address amount amount idx
00: c405f2b9b07b8d3d0a0765405fbe7d43e4dffc6d2da44b03faa6f5d042cf8b95 2.239520538000 1182103 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": 735760, "vin": [ { "gen": { "height": 735750 } } ], "vout": [ { "amount": 2239520538, "target": { "key": "c405f2b9b07b8d3d0a0765405fbe7d43e4dffc6d2da44b03faa6f5d042cf8b95" } } ], "extra": [ 1, 54, 26, 251, 77, 133, 22, 137, 243, 227, 123, 117, 180, 157, 157, 85, 92, 156, 30, 183, 193, 113, 147, 60, 101, 248, 65, 217, 105, 95, 159, 136, 184, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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