Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5095ce1818513c0bb04f03cccc8dfab69f172ea1a71441531dd6b473158dcb22

Tx prefix hash: 1821a8e1f3d23a2aa37f5392e17d0bf03b7dd75e4925e879b5888e557fd43303
Tx public key: 4ed4ac486f5e353d3f87d5a745b9e339d97a7dfa04d7b30275909b0da6899dcd
Timestamp: 1673082973 Timestamp [UCT]: 2023-01-07 09:16:13 Age [y:d:h:m:s]: 02:092:20:53:48
Block: 669440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588069 RingCT/type: yes/0
Extra: 014ed4ac486f5e353d3f87d5a745b9e339d97a7dfa04d7b30275909b0da6899dcd02110000000452542ceb000000000000000000

1 output(s) for total of 3.714217572000 dcy

stealth address amount amount idx
00: 01f30d59837dc379c2c3d14db404789d06950bcf12cadd99b2c48e867f66d866 3.714217572000 1110757 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": 669450, "vin": [ { "gen": { "height": 669440 } } ], "vout": [ { "amount": 3714217572, "target": { "key": "01f30d59837dc379c2c3d14db404789d06950bcf12cadd99b2c48e867f66d866" } } ], "extra": [ 1, 78, 212, 172, 72, 111, 94, 53, 61, 63, 135, 213, 167, 69, 185, 227, 57, 217, 122, 125, 250, 4, 215, 179, 2, 117, 144, 155, 13, 166, 137, 157, 205, 2, 17, 0, 0, 0, 4, 82, 84, 44, 235, 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