Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a883c0a39afd5d5f018ed500e8d3da21955d1d949142ff73330f8734d8c8b914

Tx prefix hash: 9607230aad6a26847b4bd7f2370d93083d88700d1cb052d6a3c080c210333e59
Tx public key: 267457b5b012f02cdcba2eefa9b2dfc290f09b18bf93f43c60cf0c8063ab1b57
Timestamp: 1738846725 Timestamp [UCT]: 2025-02-06 12:58:45 Age [y:d:h:m:s]: 00:287:01:31:24
Block: 1213372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202916 RingCT/type: yes/0
Extra: 01267457b5b012f02cdcba2eefa9b2dfc290f09b18bf93f43c60cf0c8063ab1b5702110000003227ff1f91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 049e5975cfb945e0a6ac66b918b99458a3664869707ab2b39a201f1d749e2743 0.600000000000 1700151 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": 1213382, "vin": [ { "gen": { "height": 1213372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "049e5975cfb945e0a6ac66b918b99458a3664869707ab2b39a201f1d749e2743" } } ], "extra": [ 1, 38, 116, 87, 181, 176, 18, 240, 44, 220, 186, 46, 239, 169, 178, 223, 194, 144, 240, 155, 24, 191, 147, 244, 60, 96, 207, 12, 128, 99, 171, 27, 87, 2, 17, 0, 0, 0, 50, 39, 255, 31, 145, 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