Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5eb7c225de0504f6d93baa96bf35da315cc85eaf7595d19ee68160954544639a

Tx prefix hash: f2ace57f6b5b58d5431d7f9ffbe413ef81de35bf12db2466787fb9ee6e7116bb
Tx public key: 30f7014fce9f19174e8be2ac6b86f0f67cfd41b8f832bf2a5389c4a3082ea36c
Timestamp: 1685571424 Timestamp [UCT]: 2023-05-31 22:17:04 Age [y:d:h:m:s]: 01:300:06:01:50
Block: 772379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475761 RingCT/type: yes/0
Extra: 0130f7014fce9f19174e8be2ac6b86f0f67cfd41b8f832bf2a5389c4a3082ea36c02110000000133af99f4000000000000000000

1 output(s) for total of 1.693510578000 dcy

stealth address amount amount idx
00: 00f139f44ecb50548d965c00bce632dc44c8646e3fd74604ec77ad9628fef9cc 1.693510578000 1221780 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": 772389, "vin": [ { "gen": { "height": 772379 } } ], "vout": [ { "amount": 1693510578, "target": { "key": "00f139f44ecb50548d965c00bce632dc44c8646e3fd74604ec77ad9628fef9cc" } } ], "extra": [ 1, 48, 247, 1, 79, 206, 159, 25, 23, 78, 139, 226, 172, 107, 134, 240, 246, 124, 253, 65, 184, 248, 50, 191, 42, 83, 137, 196, 163, 8, 46, 163, 108, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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