Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45251bf1466e58b89214cc8880992506845b46f25875b86f1f6e6ff077ff9d36

Tx prefix hash: 3efd258a7fff5282e4cd720bbd31b0dd18eee6f8efa742a7a77a6f304a1a7bf5
Tx public key: bb92cc5773149a9fea739b28fe420bb8defbd79a82d1b2692f11000c46e4409d
Timestamp: 1751480317 Timestamp [UCT]: 2025-07-02 18:18:37 Age [y:d:h:m:s]: 00:135:06:28:05
Block: 1317395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94917 RingCT/type: yes/0
Extra: 01bb92cc5773149a9fea739b28fe420bb8defbd79a82d1b2692f11000c46e4409d021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2db0d2ad52ab62bca657bae4de1f0ec1de62e7e8c8bc31d4b3ac94db398874c 0.600000000000 1805062 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": 1317405, "vin": [ { "gen": { "height": 1317395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2db0d2ad52ab62bca657bae4de1f0ec1de62e7e8c8bc31d4b3ac94db398874c" } } ], "extra": [ 1, 187, 146, 204, 87, 115, 20, 154, 159, 234, 115, 155, 40, 254, 66, 11, 184, 222, 251, 215, 154, 130, 209, 178, 105, 47, 17, 0, 12, 70, 228, 64, 157, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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