Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e7e4fa069fe10538e066f884fff66875545cb2f2bab688a09cfb98721dfb83a

Tx prefix hash: d53c576e3e1fa21e5499dd97d7406b816cd0c9bde49aa7ebb1ba2acfa4ba01fd
Tx public key: 498c4c0f0fb62ca931aed4a06701b9bd71a66776e4c9fce589cac1299df0b7b6
Timestamp: 1664402084 Timestamp [UCT]: 2022-09-28 21:54:44 Age [y:d:h:m:s]: 02:173:12:55:32
Block: 597750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645622 RingCT/type: yes/0
Extra: 01498c4c0f0fb62ca931aed4a06701b9bd71a66776e4c9fce589cac1299df0b7b6021100000001faf35c9c000000000000000000

1 output(s) for total of 6.418955504000 dcy

stealth address amount amount idx
00: 08eaf7a0d6cee3882f09b178bafe28227e5cc39cd9d4a1b88fbc4e4ba0b77f40 6.418955504000 1033279 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": 597760, "vin": [ { "gen": { "height": 597750 } } ], "vout": [ { "amount": 6418955504, "target": { "key": "08eaf7a0d6cee3882f09b178bafe28227e5cc39cd9d4a1b88fbc4e4ba0b77f40" } } ], "extra": [ 1, 73, 140, 76, 15, 15, 182, 44, 169, 49, 174, 212, 160, 103, 1, 185, 189, 113, 166, 103, 118, 228, 201, 252, 229, 137, 202, 193, 41, 157, 240, 183, 182, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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