Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84edf4ec28835e4b1df5a6f965d75435c655e8ba7a5b8bf940121f2118a15378

Tx prefix hash: 873fe93f772e9d1bbed522d33c61615f1020c35c6109640b6a878733ef908d58
Tx public key: 54aa1d4da6925b798f3f7b4e3f656f199acedb3281275e6f603f09c6775b59e2
Timestamp: 1677809591 Timestamp [UCT]: 2023-03-03 02:13:11 Age [y:d:h:m:s]: 02:029:14:08:51
Block: 708659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 542714 RingCT/type: yes/0
Extra: 0154aa1d4da6925b798f3f7b4e3f656f199acedb3281275e6f603f09c6775b59e202110000000233af99f4000000000000000000

1 output(s) for total of 2.753711608000 dcy

stealth address amount amount idx
00: cc87542767676954cf0fe22caa657db5482c88aecc830163db0fde5762f5fb5d 2.753711608000 1152566 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": 708669, "vin": [ { "gen": { "height": 708659 } } ], "vout": [ { "amount": 2753711608, "target": { "key": "cc87542767676954cf0fe22caa657db5482c88aecc830163db0fde5762f5fb5d" } } ], "extra": [ 1, 84, 170, 29, 77, 166, 146, 91, 121, 143, 63, 123, 78, 63, 101, 111, 25, 154, 206, 219, 50, 129, 39, 94, 111, 96, 63, 9, 198, 119, 91, 89, 226, 2, 17, 0, 0, 0, 2, 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