Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2e461135130cb53e3a9b34d6623e81afee391b0366b0754a08d39babd184b79

Tx prefix hash: 76e5aad0da0b99df11732cfb86c0fb839e816d3d79e38a42660cd6a28512a937
Tx public key: 8a7fd0339c5f074aa2ff5efe172673ac5a46038f3a18d78bf131c7c181415099
Timestamp: 1751132314 Timestamp [UCT]: 2025-06-28 17:38:34 Age [y:d:h:m:s]: 00:178:00:19:10
Block: 1314669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125361 RingCT/type: yes/0
Extra: 018a7fd0339c5f074aa2ff5efe172673ac5a46038f3a18d78bf131c7c181415099021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cff97ad5fa1425e04fd0b2061a88e70630d6cd8417647ef23eb9fc30b8b90f8 0.600000000000 1802320 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": 1314679, "vin": [ { "gen": { "height": 1314669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cff97ad5fa1425e04fd0b2061a88e70630d6cd8417647ef23eb9fc30b8b90f8" } } ], "extra": [ 1, 138, 127, 208, 51, 156, 95, 7, 74, 162, 255, 94, 254, 23, 38, 115, 172, 90, 70, 3, 143, 58, 24, 215, 139, 241, 49, 199, 193, 129, 65, 80, 153, 2, 17, 0, 0, 0, 2, 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