Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b80f8ba0fc318ced045f72c4a8a6b59aacd8999bfe8e47af8cbd432097076dc0

Tx prefix hash: 73b63a2870ab5bd34a2a8f15c9add39e9ee148896f75a3cd172cf6578d721fa4
Tx public key: 5e932ab802a255a538c0a0c4462352574eca82bd9f40c621825f82c9b28bf8ef
Timestamp: 1706356687 Timestamp [UCT]: 2024-01-27 11:58:07 Age [y:d:h:m:s]: 01:080:16:33:40
Block: 944423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318765 RingCT/type: yes/0
Extra: 015e932ab802a255a538c0a0c4462352574eca82bd9f40c621825f82c9b28bf8ef0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0f24bc5bd2bd54509963684f1cca3047d1bc44fba49ea3c761ac7e2758b1bf8 0.600000000000 1402659 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": 944433, "vin": [ { "gen": { "height": 944423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0f24bc5bd2bd54509963684f1cca3047d1bc44fba49ea3c761ac7e2758b1bf8" } } ], "extra": [ 1, 94, 147, 42, 184, 2, 162, 85, 165, 56, 192, 160, 196, 70, 35, 82, 87, 78, 202, 130, 189, 159, 64, 198, 33, 130, 95, 130, 201, 178, 139, 248, 239, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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