Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9755d5bcaf5687a749c376108e79c6e68d944ffe06566e08da9fa45d4a5bb03b

Tx prefix hash: 03f4b8b066344201f9aa678340cb3ad21b0ee2de10e8adba4a5ae7b3f8851fb7
Tx public key: c32840f6dbf0ca5b7d2ad902b1b8a0a59269605e61c30cdb38064104cb129bfe
Timestamp: 1751398244 Timestamp [UCT]: 2025-07-01 19:30:44 Age [y:d:h:m:s]: 00:140:18:37:49
Block: 1316738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98832 RingCT/type: yes/0
Extra: 01c32840f6dbf0ca5b7d2ad902b1b8a0a59269605e61c30cdb38064104cb129bfe021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c1553c5847f93790db6eaced248077c2caa33547c0bec553b2289dff617ff72 0.600000000000 1804401 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": 1316748, "vin": [ { "gen": { "height": 1316738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c1553c5847f93790db6eaced248077c2caa33547c0bec553b2289dff617ff72" } } ], "extra": [ 1, 195, 40, 64, 246, 219, 240, 202, 91, 125, 42, 217, 2, 177, 184, 160, 165, 146, 105, 96, 94, 97, 195, 12, 219, 56, 6, 65, 4, 203, 18, 155, 254, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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