Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8809f1422575138aea7d8f7a5cac5dcfb60e49dd5404a13032108ba02af5f7ff

Tx prefix hash: 7d24d8adf33fca1951b4723ae51053af357c58ae0d154072ad6bdd688d747d65
Tx public key: e976b342e348bb547cbf30117dfcab56250e1e3d81e893eb0d6f9d1e82c7e388
Timestamp: 1641080718 Timestamp [UCT]: 2022-01-01 23:45:18 Age [y:d:h:m:s]: 02:332:15:59:19
Block: 408492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755871 RingCT/type: yes/0
Extra: 01e976b342e348bb547cbf30117dfcab56250e1e3d81e893eb0d6f9d1e82c7e388021100000035cda45b65000000000000000000

1 output(s) for total of 27.195482591000 dcy

stealth address amount amount idx
00: b07d1cf60b8cd1df51019cb22a3a28cc4944944f71d817079689e257cde0abfe 27.195482591000 810561 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": 408502, "vin": [ { "gen": { "height": 408492 } } ], "vout": [ { "amount": 27195482591, "target": { "key": "b07d1cf60b8cd1df51019cb22a3a28cc4944944f71d817079689e257cde0abfe" } } ], "extra": [ 1, 233, 118, 179, 66, 227, 72, 187, 84, 124, 191, 48, 17, 125, 252, 171, 86, 37, 14, 30, 61, 129, 232, 147, 235, 13, 111, 157, 30, 130, 199, 227, 136, 2, 17, 0, 0, 0, 53, 205, 164, 91, 101, 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