Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 118d47ad63dfbaca67ae5be87ead30fae001e32b1c8fb2ff4226444b18dfe4dd

Tx prefix hash: 44f00e0e710a80b5eb213961a580bd49f9a8f039d0e18561318ae822bd2a169f
Tx public key: 191ff2d306198b069b5c1faf96c1dcc4fcad30171d94e58c92c0ed2964719b7c
Timestamp: 1751480594 Timestamp [UCT]: 2025-07-02 18:23:14 Age [y:d:h:m:s]: 00:182:11:39:09
Block: 1317400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128720 RingCT/type: yes/0
Extra: 01191ff2d306198b069b5c1faf96c1dcc4fcad30171d94e58c92c0ed2964719b7c021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0819dca7ab56255342fa0d7989802bdf68b6da1e8a82d7d07c4d261777029383 0.600000000000 1805067 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": 1317410, "vin": [ { "gen": { "height": 1317400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0819dca7ab56255342fa0d7989802bdf68b6da1e8a82d7d07c4d261777029383" } } ], "extra": [ 1, 25, 31, 242, 211, 6, 25, 139, 6, 155, 92, 31, 175, 150, 193, 220, 196, 252, 173, 48, 23, 29, 148, 229, 140, 146, 192, 237, 41, 100, 113, 155, 124, 2, 17, 0, 0, 0, 3, 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