Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d51b3438200be88a13fa63812fe99e11aecc536368e7729d9b4996ac25ca9b

Tx prefix hash: f1f29b7ced0c792c2937a3cd4a3c07ff8bd07d918e161f565dc9fee53a680cec
Tx public key: c8cf7fe8b2c21e8dfa2ec40434f9f11d66d0b7acc32e81f7a92e80abe12204b3
Timestamp: 1750901045 Timestamp [UCT]: 2025-06-26 01:24:05 Age [y:d:h:m:s]: 00:141:12:16:46
Block: 1312863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99115 RingCT/type: yes/0
Extra: 01c8cf7fe8b2c21e8dfa2ec40434f9f11d66d0b7acc32e81f7a92e80abe12204b30211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07efeed6bf9a0c0fc6087509ba3709eb427af0ea7aa3ec00cf164c501779557a 0.600000000000 1800498 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": 1312873, "vin": [ { "gen": { "height": 1312863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07efeed6bf9a0c0fc6087509ba3709eb427af0ea7aa3ec00cf164c501779557a" } } ], "extra": [ 1, 200, 207, 127, 232, 178, 194, 30, 141, 250, 46, 196, 4, 52, 249, 241, 29, 102, 208, 183, 172, 195, 46, 129, 247, 169, 46, 128, 171, 225, 34, 4, 179, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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