Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8b4e1559877849ac5029c59e543e26e29e2f81251d77a013af02692a87a27e2

Tx prefix hash: 67ddc90bba355c29583f901beafdd204bcad79dce2d76ac6efac9db0f3f196dd
Tx public key: c38d8db29e112101e6c84f65d9d6961a32c7d951cb8ecbb1ef92b92fb78f1e99
Timestamp: 1684612788 Timestamp [UCT]: 2023-05-20 19:59:48 Age [y:d:h:m:s]: 01:237:13:30:30
Block: 764434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431218 RingCT/type: yes/0
Extra: 01c38d8db29e112101e6c84f65d9d6961a32c7d951cb8ecbb1ef92b92fb78f1e9902110000000275e3f0e9000000000000000000

1 output(s) for total of 1.799429063000 dcy

stealth address amount amount idx
00: caac4090f474ac6958b47f0bbd1504dd5c889b0f5fcd293f4d1b64a8c9070040 1.799429063000 1213351 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": 764444, "vin": [ { "gen": { "height": 764434 } } ], "vout": [ { "amount": 1799429063, "target": { "key": "caac4090f474ac6958b47f0bbd1504dd5c889b0f5fcd293f4d1b64a8c9070040" } } ], "extra": [ 1, 195, 141, 141, 178, 158, 17, 33, 1, 230, 200, 79, 101, 217, 214, 150, 26, 50, 199, 217, 81, 203, 142, 203, 177, 239, 146, 185, 47, 183, 143, 30, 153, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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