Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f720ff0c1e3364dea1730e4e0be2adca18da8d987f988df74f7d190b217fe91

Tx prefix hash: e3c91a4b26e0a6592072e41b583c4e1f8b2a98c0a1d225fb950b5b7d57891a18
Tx public key: 708fe12b646b529ede99531a14d151b48dcadc6f5db5e655ffa5380cd5a6ef4e
Timestamp: 1722127407 Timestamp [UCT]: 2024-07-28 00:43:27 Age [y:d:h:m:s]: 00:285:15:25:32
Block: 1075188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204079 RingCT/type: yes/0
Extra: 01708fe12b646b529ede99531a14d151b48dcadc6f5db5e655ffa5380cd5a6ef4e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 805d82d27c0bc935b252144744d3a13b6628bc42c2b0834dbce4eaf5222632e8 0.600000000000 1547711 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": 1075198, "vin": [ { "gen": { "height": 1075188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "805d82d27c0bc935b252144744d3a13b6628bc42c2b0834dbce4eaf5222632e8" } } ], "extra": [ 1, 112, 143, 225, 43, 100, 107, 82, 158, 222, 153, 83, 26, 20, 209, 81, 180, 141, 202, 220, 111, 93, 181, 230, 85, 255, 165, 56, 12, 213, 166, 239, 78, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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