Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1775da4fd0bb2f5b5957990ef0d3748b634d9aedb3efdcfd7365b0609e6d3f4

Tx prefix hash: e9fa30612643f09ebeda8a66ed73f07ff61a3ec35f587ffffedc6e1aa8a5dd60
Tx public key: f028dfd005b0ca5ab91890ef405f3b0f41ba88d000b3d3d9db7bfccd316bcb5b
Timestamp: 1582439243 Timestamp [UCT]: 2020-02-23 06:27:23 Age [y:d:h:m:s]: 04:344:19:24:14
Block: 70748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138715 RingCT/type: yes/0
Extra: 01f028dfd005b0ca5ab91890ef405f3b0f41ba88d000b3d3d9db7bfccd316bcb5b02110000000112c4732d000000000000000000

1 output(s) for total of 357.765100917000 dcy

stealth address amount amount idx
00: fa19f2c4eaeb2d1d438856aec35a2702bb32d4509d589b2c9183574c08bd92aa 357.765100917000 130698 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": 70758, "vin": [ { "gen": { "height": 70748 } } ], "vout": [ { "amount": 357765100917, "target": { "key": "fa19f2c4eaeb2d1d438856aec35a2702bb32d4509d589b2c9183574c08bd92aa" } } ], "extra": [ 1, 240, 40, 223, 208, 5, 176, 202, 90, 185, 24, 144, 239, 64, 95, 59, 15, 65, 186, 136, 208, 0, 179, 211, 217, 219, 123, 252, 205, 49, 107, 203, 91, 2, 17, 0, 0, 0, 1, 18, 196, 115, 45, 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